On 04 Dec 2009, at 12:42, Peter De Berdt wrote: >> >> Does that mean I need to change any more code than is in my model ? >> >> I did set GC.start inside Photo.save in the controller. The >> situation >> does not go out of hand any more, but the app is using quite a lot of >> memory none the less. > > RMagick is quite memory hungry. RMagick 2 does have automatic > garbage collection, but it seems you might be running into this > gotcha: > > http://rubyforge.org/forum/forum.php?thread_id=1374&forum_id=1618 >
One more note on this. Since you seem to be just thumbnailing, you could as well use another processor if memory is valuable. If you need to do extra processing like applying filters and constructing an image out of several other ones, then you're best off with RMagick. There's nothing more to it than making sure the processor (minimagick, imagescience, gd2, core image on macos x servers) is installed correctly and explicitly defining it in your model. Otherwise attachment_fu will see if it can use one of them in this order: @@default_processors = %w(ImageScience Rmagick MiniMagick Gd2 CoreImage). Best regards Peter De Berdt -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
