http://212.47.245.38:19999/#menu_cpu_submenu_utilization;after=1491602886000;before=1491606891000;theme=slate;help=true
Even with 2 sidekiq processes and 40 threads it doesn't use more than 60% CPU.
Are sidekiq's threads... single-threaded? I'll assume it's like python, not really made for multi-threading...
@CobaltVelvet I haven't been using ruby for a while but that's how it used to be with the GIL/GVL global locks. A quick search implies that's still how it works, so you're right that you're only going to get concurrency when a thread is waiting on I/O, etc. So you'd probably be better off starting more processes if you need to scale and you think CPU is becoming a bottleneck as far as I can tell
@CobaltVelvet I'm a bit curious how all this would do running on jruby. Looks like there's some posts out there implying sidekiq is supported and gets a boost. So many possible things to try to look into about masto this weekend I don't know how to pick 🤔
