@francois that's mostly what the topic centers around.
I guess the conclusion I'm circling around is: using Ruby Threads is performatively worse than using multiple processes. Because Ruby threads still uses OS kernel switching AND also has to do GVL locking/unlocking on top of that.
This is not quite a Unicorn vs Puma thing, but that's a lot of the context of these thoughts. Cause other than sharing resources (memory, db connections) multiple processes seems better for perf.
=> More informations about this toot | View the thread | More toots from bensheldon@ruby.social
=> View francois@ruby.social profile
text/geminiThis content has been proxied by September (ba2dc).