You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was observing the behavior of resque-pool on a Mac.
We have resque pool forking 5 child processes doing nothing.
Right after successful forking, the parent resque-pool process took 120M and each child resque process took less than 20M. But after 5 minutes, memory start growing up to 110M per child resque process even though they were not doing anything. This led to aggressive memory usage in Heroku causing memory to keep getting swapped out to disk. Could you recommend a solution? I'm looking for a way to figure out the reason why idle child process keeps eating memory as well as a way to kill and refork them if memory has been grown too much.
The text was updated successfully, but these errors were encountered:
I was observing the behavior of resque-pool on a Mac.
We have resque pool forking 5 child processes doing nothing.
Right after successful forking, the parent resque-pool process took 120M and each child resque process took less than 20M. But after 5 minutes, memory start growing up to 110M per child resque process even though they were not doing anything. This led to aggressive memory usage in Heroku causing memory to keep getting swapped out to disk. Could you recommend a solution? I'm looking for a way to figure out the reason why idle child process keeps eating memory as well as a way to kill and refork them if memory has been grown too much.
The text was updated successfully, but these errors were encountered: