-
I have attempted to use the new feature included in Puma 6.4.0 (#3209 ) in my Rails application. For certain requests that take a considerable amount of time, I create a background process using the following code snippet:
I hope there is a solution for this, since it will help in reducing memory problem. Currently, after processing requests that consume a significant amount of RAM, the worker not returning the memory back to the OS. Any assistance is highly appreciated. Thank you. Extra info: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It is whatever worker are processing the request. If you spawn background threads, I don't think it is a good idea to also use I think you should consider a background job system like https://github.com/resque/resque or https://github.com/sidekiq/sidekiq over just doing |
Beta Was this translation helpful? Give feedback.
It is whatever worker are processing the request.
If you spawn background threads, I don't think it is a good idea to also use
idle_timeout
as you have discovered.I think you should consider a background job system like https://github.com/resque/resque or https://github.com/sidekiq/sidekiq over just doing
Thread.new
for things that take a long time.