Post by @jorijn
Noticed occasional spikes in latency for #tootcommunity. We were just setting `requests` on sidekiq runners to help scheduling, but don't have limits. When the default queue started filling, the sidekiq workers took all the available CPU cycles resulting in poor performance for the end-users. Solution: Split up the node pool, add taints/tolerations so only the sidekiq processes run on those machines.