rubygems-update requires Ruby version >= 3.0.0

Questions / Help Build debugging
,
8

I was looking at Managing Redis rate limits on Sidekiq and Rails and it looks like depending on my concurrency the checks that sidekiq makes for more items in the Redis instance may be too high.

Here are my configs:

Sidekiq

:concurrency: <%= ENV["SIDEKIQ_MAX_THREADS"] || 8 %>
:timeout: 8

:queues:
  - ["high", 6]
  - ["default", 4]
  - ["mailer", 2]
  - ["low", 1]

max_retries: 0

I have made the following updates based on what @jsierles suggested in the post I linked above:

config/initializers/sidekiq.rb

Sidekiq.configure_server do
  Sidekiq::BasicFetch::TIMEOUT = 15
end

config/sidekiq.yml

:concurrency: <%= ENV["SIDEKIQ_MAX_THREADS"] || 1 %>
:timeout: 8

:queues:
  - ["high", 6]
  - ["default", 4]
  - ["mailer", 2]
  - ["low", 1]

max_retries: 0

And then I set my SIDEKIQ_MAX_THREADS environment variable to 1.

This is what I think is happening:

My concurrency is too high for the needs of my system. This is leading to too many commands being sent to Redis to check for items to process. This would explain why Bandwidth, Storage and Cost numbers in my Redis dashboard are so low while Commands are through the roof.