Heroku worker dyno giving R14 errors - problems with memory management - rmagick memory limit options

Question

I've tried to use a 2X worker dyno, waiting to not get R14 errors, but this is the result:

2013-06-04T13:03:30.723260+00:00 heroku[worker.1]: Process running mem=1047M(102.3%)
2013-06-04T13:03:30.723260+00:00 heroku[worker.1]: Error R14 (Memory quota exceeded)

However, the task for the worker is finished successfully.

Questions:

How can I decrease the needed memory for my job? - I'm using rmagick gem to convert a list of images to a single multipage pdf.
How dangerous is to keep the process like this (with R14 errors) as the final job is finishing successfully?

Thanks in advance

Are you only running 1 of these jobs at a time in sidekiq? That is, does 1 job take 1 gig of memory? — Jesse Wolgamott, Jun 04 '13 at 14:32
It seems like the gem rmagick which I'm also using has memory leaks: http://stackoverflow.com/questions/958681/how-to-deal-with-memory-leaks-in-rmagick-in-ruby — josal, Jun 05 '13 at 09:21

josal · Accepted Answer · 2015-03-16T13:00:27.380

5

I finally found a solution. The problem was with rmagick. It gets all the memory it sees available. It doesn't matter if you use a 2X worker dyno instead of a 1X one. It grows to the maximum available resources. So, we have to set a limit. But in my case not all the limits worked.

You can make a system call directly this way:

convert -limit memory 0 -limit map 0 list_of_input_files output_file

This way, you avoid to use the memory cache, going directly to the disk cache. This is the only way I've found to avoid R14 errors in heroku. With other combinations like -limit memory 32 -limit map 64 or similar, it always gave me errors. I took the idea from here.

Of course, you could always use the rmagick library with this lines, however it didn't work for me and I did use the syscall approach explained before:

Magick.limit_resource(:memory, 0)
Magick.limit_resource(:map, 0)

UPDATE: I've used the nice command to ensure more priority. It seems it improves, but eventually I'm getting R14 errors, but it's true they are not so often (even with the same file!).

edited Mar 16 '15 at 13:00

answered Jun 10 '13 at 07:31

josal

452
7
15

I tried it but I can't remember now why I didn't choose it. Thanks anyway. – josal Sep 11 '13 at 14:01
Sorry but where are you calling this system call from ? – Fabrice Carrega Jun 08 '14 at 18:43
1

system() function in ruby :-) – josal Jun 09 '14 at 07:36
Simple but efficient ! Thanks ! – Fabrice Carrega Jun 09 '14 at 12:22
Not only rmagick, I guess, but a combination of it and heroku... At last, I had to adapt to heroku specs, that's why I fined rmagick – josal Jul 03 '14 at 07:45
Did you manage to eliminate r14 errors eventually? with `-limit memory 0 -limit map 0` – Nick Ginanto Mar 15 '15 at 13:12
@NickGinanto Yes, I did, but maybe with the newer stack or with other buildback you can try it again and fine rmagick better. – josal Mar 16 '15 at 12:55

score 0 · Answer 2 · answered Oct 27 '17 at 13:11

0

A little late for the party, but in my case the garbage collector was my savior. Just run GC.start after each job.

answered Oct 27 '17 at 13:11

Igor

1,253
1
25
34

Thanks for your answer. – josal Nov 03 '17 at 10:44

Heroku worker dyno giving R14 errors - problems with memory management - rmagick memory limit options

2 Answers2