that doesn't feel well

geography wrote:

I'm resizing it too. But that is not where it dies.
It dies right before I write it to disk (With Magick::Image.write from RMagick)

I meant "resizing" as anything to do with RMagick. There've been a couple threads on this, search around. Resizing you image before upload or not using RMagick and instead using ImageMagick via the commandline might or might not work.... basically you can't do much, unfortunately.

Using open(fname, 'w'){|f|f.write img.to_blob} has the same problem... I guess I'll try and run it from the command line but that seems like a drastic step. Why is the memory so limited, shouldn't the server be able to save 500k files, or does imageMagick have a very high overhead?

So what i've learned so far...

TextDrive has a memory limit.
-When using RMagick in a rails app running with fcgi and lighttpd this memory limit is exceeded.
-When the memory limit is exceeded the fcgi process is killed (No expcetions caught or anything in Ruby... the process ends)
-The problem occurs when writing images to disk (With either File.open or Image.write)
-The problem still occurs if I call GC.starts after RMagick calls

Here is what I don't get...
-Why is the memory limit so low (Or why does a simple RMagick call take up so much memory? My dispatch procs take up around 50 megs, I can't imagine that opening a 600k file would come close to using that much memory)
-Would putting my RMagick code in a different thread allow me to have more memory at my disposal?

So after some investigation it seems like RMagick is a total memory hog.

I load a 750k image with this tiny standalone ruby program...

image = nil
open(filepath) do |f|

image = Magick::Image.from_blob(f.read).first
end
image.write("image.jpg")

Monitoring the mem usage (using top) I get this 8th column is mem usuage

#File being downloaded
7198 ruby 7.6% 0:04.83 2 15 60 3.37M+ 2.65M 4.88M+ 44.5M+
7198 ruby 14.4% 0:05.01 2 15 68 18.1M+ 2.73M+ 20.0M+ 80.9M+
7198 ruby 35.0% 0:05.49 2 15 67 41.8M+ 2.73M 43.7M+ 80.8M-

#File being loading into Magick::Image
7198 ruby 0.1% 0:05.49 2 15 67 41.8M 2.73M 43.7M 80.8M-
7198 ruby 0.1% 0:05.49 2 15 67 41.8M 2.73M 43.7M 80.8M-

#File being written to disk
7198 ruby 3.4% 0:05.53 2 15 72 43.4M+ 2.73M 45.3M+ 122M+
7198 ruby 55.9% 0:06.29 2 15 72 61.1M+ 2.73M 63.0M+ 122M
7198 ruby 48.4% 0:06.93 2 15 72 76.1M+ 2.73M 78.1M+ 122M
7198 ruby 48.2% 0:07.55 2 15 67 42.5M- 2.73M 44.4M- 80.8M-

So I guess the moral is RMagick eats up a ton of memory. I can't really see anyway around this problem though, maybe using the command line would eat up less memory (which is what I'll try next)

Last edited by geography (Today 21:29:17)