News for hackers. Stuff that matters.
Re:Rescuing Resque again (2015) by AznHisoka on Friday January 15, 2016 @01:40PM (#10911174)
It matters how many of these tasks can be completed in a fixed amount of time. Creating 50 processes requires more resources than 1 process with 50 threads.
Re:Rescuing Resque again (2015) by sanderjd on Friday January 15, 2016 @02:37PM (#10911552)
Yeah, Sidekiq is an obvious switch once you find yourself running 20 500MB Rails processes just because you want to be able to handle a few simple tasks concurrently. If you have a few big, long-running, CPU-intensive background jobs, then the benefits are less clear, but if you have lots of small, short running jobs where you're mostly interested in throughput, then Sidekiq makes a lot more sense.
Re:Rescuing Resque again (2015) by otterley on Friday January 15, 2016 @06:05PM (#10912953)
Resque-pool (https://github.com/nevans/resque-pool) -- which every Resque user should be using -- loads your process first, then forks the workers. Forking uses copy-on-write semantics, so as long as you're loading everything before forking, you're conserving a great deal of otherwise wasted memory on what would be shareable pages.