Sidekiq Not Deallocating Memory After Workers Have Finished

Sidekiq not deallocating memory after workers have finished

Mike Perham who wrote Sidekiq addressed this here: http://www.mikeperham.com/2009/05/25/memory-hungry-ruby-daemons/

tl;dr version: MRI will not give the memory back, the most you can do is control the heap, and to do that, Ruby Enterprise Edition was suggested.

Don't know that any of this helps, but that is the situation - straight from the horse's mouth.

Sidekiq worker is leaking memory

I didn't find the cause for the memory leak in sidekiq, but I found a away to get a way from sidekiq.

I have modified git-tf to have server command that accepts command from redis queue, it removes lot of complexity from my code.

The modified version of git-tf is here:
https://github.com/yosy/gittf

I will add documentation later about the sever command when I will fix some bugs.

Related Topics