Skip to content
Snippets Groups Projects
Select Git revision
  • move-member-approval-to-ee
  • trizzi-master-patch-0b71
  • pl-undercover-gems
  • irinabron/521403-custom-stats-autovacuum-settings
  • 515383-mark-tables-exempt-from-sharding
  • lealasmith-duo-workflow-set_up-take2
  • sq-update-code-suggestions-setup-docs
  • jy-ai-gateway-url-in-database
  • tbulva-long-line-bug
  • 513340-web-ide-should-be-distinguished-from-web-ui-in-duo-chat-slash-commands-dashboard
  • master default protected
  • rails-next protected
  • ruby-next protected
  • docs-uc-fix-usage-of-since-pt1
  • georgekoltsov/restartable-project-import
  • 499586-automate-search-validation
  • 516058_move_renamed_table_dict_to_deleted
  • id-q-send-web-hook-event
  • 493994-aqualls-spam-image
  • id-amazon-q-virtual-integration
  • v17.7.6-ee protected
  • v17.8.4-ee protected
  • v17.9.1-ee protected
  • v17.8.3-ee protected
  • v17.7.5-ee protected
  • v17.9.0-ee protected
  • v17.9.0-rc42-ee protected
  • v17.6.5-ee protected
  • v17.7.4-ee protected
  • v17.8.2-ee protected
  • v17.6.4-ee protected
  • v17.7.3-ee protected
  • v17.8.1-ee protected
  • v17.8.0-ee protected
  • v17.7.2-ee protected
  • v17.8.0-rc42-ee protected
  • v17.5.5-ee protected
  • v17.6.3-ee protected
  • v17.7.1-ee protected
  • v17.7.0-ee protected
40 results

sidekiq_cluster.rb

  • Stan Hu's avatar
    73218620
    Limit sidekiq-cluster concurrency to a maximum of 50 by default · 73218620
    Stan Hu authored
    By default, sidekiq-cluster will allocate N threads for N queues specified
    on the command line, which in turn will require N + 5 Redis connections.
    Especially when used with the `--negate` flag, this can lead to using hundreds
    of Redis connections, which can lead to performance issues.
    
    This change also adds a `-m N` option to cap the number of threads. For each
    queue group, the concurrency factor will be set to min(number of queues, N).
    
    Closes #7374
    73218620
    History
    Limit sidekiq-cluster concurrency to a maximum of 50 by default
    Stan Hu authored
    By default, sidekiq-cluster will allocate N threads for N queues specified
    on the command line, which in turn will require N + 5 Redis connections.
    Especially when used with the `--negate` flag, this can lead to using hundreds
    of Redis connections, which can lead to performance issues.
    
    This change also adds a `-m N` option to cap the number of threads. For each
    queue group, the concurrency factor will be set to min(number of queues, N).
    
    Closes #7374
Code owners
Assign users and groups as approvers for specific file changes. Learn more.