You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will need to do this in a way that is opt-out, e.g. via an environment variable NO_SIDEKIQ_ENT and NO_SIDEKIQ_PRO, since the average Keygen CE installation will not pay for Sidekiq Enterprise or Sidekiq Pro.
Right now, the plan would be to replace both sidekiq-cron and sidekiq-unique-jobs with Sidekiq Enterprise's periodic and unique jobs, respectively, when it's available. When Sidekiq Enterprise is not available, we can keep sidekiq-cron, and maybe sidekiq-unique-jobs (if it's even really needed after fc1b739). When Sidekiq Pro is available but Sidekiq Enterprise is not, we can enable super_fetch and reliable_push, plus any other reliability enhancements.
The text was updated successfully, but these errors were encountered:
Let's start out by removing sidekiq-unique-jobs because I'm still seeing performance issues related to Lua scripts from it, even after my fix (and I don't have the drive to debug it anymore). We no longer use it for anything mission critical, so might as well rip it out since it's just been causing problems and outages lately and has severely limited overall scalability.
We will need to do this in a way that is opt-out, e.g. via an environment variable
NO_SIDEKIQ_ENT
andNO_SIDEKIQ_PRO
, since the average Keygen CE installation will not pay for Sidekiq Enterprise or Sidekiq Pro.Right now, the plan would be to replace both sidekiq-cron and sidekiq-unique-jobs with Sidekiq Enterprise's periodic and unique jobs, respectively, when it's available. When Sidekiq Enterprise is not available, we can keep sidekiq-cron, and maybe sidekiq-unique-jobs (if it's even really needed after fc1b739). When Sidekiq Pro is available but Sidekiq Enterprise is not, we can enable
super_fetch
andreliable_push
, plus any other reliability enhancements.The text was updated successfully, but these errors were encountered: