Request Timeouts and hitting memory quota on Heroku (Memory leak?) about image-resizer HOT 6 CLOSED

The 'Memory Quota Exceeded' could be due to the fact that we are buffering the entire objects into memory, and with a ton of images being generated, this would add up quickly - not sure if something like this would help: aws/aws-sdk-js#656

from image-resizer.

@J-Gonzalez,

A few thoughts here:

• are you running behind a CDN? much of the premise of this app is lost when no CDN is used.
• from the logs it looks like you are using a 1X dyno which may not be sufficient if your source images are very large.
• so very early on the code was attempting to stream objects as opposed to buffering them to memory but it turned out that gm was simply buffering them anyway and sharp may do something similar as some of the operations require all of the image to be used.

It is possible there could be a memory leak in the code, but my first guess is that you are asking the simple dyno to do too much work. Try scaling to a 2X and see if things improve, but as I said it is fairly dependant on your source images.

from image-resizer.

Scaling it to 2X did seem stop memory leaks. The app does climb to about 700MB of memory usage but doesn't seem to go above that.

from image-resizer.

Hello, you may want to reduce the size of libvips' operation cache on memory-constrained systems - see http://sharp.dimens.io/en/stable/api/#sharpcachememory-items

from image-resizer.

@lovell, thanks again for the input.

@J-Gonzalez if you can give this a go I would love to hear the results. image-resizer is designed to have the most sensible defaults for most cases and it sounds like setting appropriate cache sizes should be one of them.

from image-resizer.

Closing due to inactivity.

from image-resizer.