News for hackers. Stuff that matters.
Re:Ruby Garbage Collection: Still Not Ready for Production by thinkbohemian on Friday March 28, 2014 @01:10PM (#7488526)
I recommend Puma and work for Heroku, though threadafety is still a huge issue. It also pre-forks in hybrid mode which makes it super awesome. Also it takes care of slow clients!
Re:Ruby Garbage Collection: Still Not Ready for Production by midas007 on Friday March 28, 2014 @01:56PM (#7488868)
It's also way, way cheaper in terms of ram.

We fire up sidekiq and clockwork in threads within the puma process rather than take ~ 100 MiB/process hit of running them separately.

Re:Ruby Garbage Collection: Still Not Ready for Production by evilduck on Friday March 28, 2014 @03:09PM (#7489316)
Is there any blog post or tutorial you can point to that explains how to do that?

If not, I would love it if you wrote one. :)

Re:Ruby Garbage Collection: Still Not Ready for Production by midas007 on Friday March 28, 2014 @08:32PM (#7490868)
Done, in the form of a reusable rails template. :)

https://github.com/steakknife/rails41rc_plus_hacks_and_threa...

Feedback requested in the issue tracker. Anything that seems out of place.

Re:Ruby Garbage Collection: Still Not Ready for Production by midas007 on Friday March 28, 2014 @04:03PM (#7489635)
Sure. I even spawn other threads as ghetto thread supervision.