Sidekiq is available in Gaelic!
https://mastodon.online/@gunchleoc@ailbhean.co-shaoghal.net/114635301038793788
#sidekiq
🚀 Oh joy, another groundbreaking revelation: someone built a Ruby on Rails app with.... wait for it... #PostgreSQL and Redis! 🎉 Let's all pretend we're not asleep as they dazzle us with their cutting-edge use of #Sidekiq and Tailwind CSS. Clearly, they've single-handedly revolutionized web development in 2025 with this mind-blowing use of, um, Devise and OAuth. 🙄
https://attendlist.com/blog/production-rails-stack #RubyOnRails #Redis #WebDevelopment #TailwindCSS #HackerNews #ngated
Perfm is an interesting new tool for determining the optimal concurrency for your Ruby application.
https://github.com/bigbinary/perfm #ruby #sidekiq
What's the recommendation for #testing #Sidekiq client middleware? There is explicit guidance, and baked in support for `ServerMiddleware`, but I've not found much for building client middleware. So, I started a Discussion on GitHub: https://github.com/sidekiq/sidekiq/discussions/6698
So many dead instances on #Sidekiq.
Whether or not you use Judoscale, you should check out Judoscale guides to configuring #Rails for production, scaling #Sidekiq, and understanding request queue time.
👉 https://judoscale.com/blog/opinionated-guide-to-configuring-rails-on-heroku
I wish there was a way to consolidate findings of dead/error'd shit in #SideKiq dashboard.
Don't just tell me there's a 1000 failed jobs.
Group and count and drill that shit down into common errors... HTTP ConnectionError / TimeoutError / TypeError etc (or deeper). Even better if it could group specific problem domains.
Man there's a zillion things I'd want changed in this dashboard. Is it supposed to feel like a minimum viable product? Are there nicer dashboards/frontends for Sidekiq?
Server here is running slow today, not sure if it's still recovering from yesterday's downtime, or what. 🤔 #sidekiq #MastoAdmin
I recorded some live video yesterday of my Mastodon server attempting to catch up after some downtime/restore from snapshot. #sidekiq #mastodon #software
It's always great to see @rosa and she talked about her #SolidQueue implementation at #rubycommunityconference in #krakow.
She also gave a shout-out to @bensheldon's #goodjob and mentioned how @getajobmike's @sidekiq is blazingly fast.
#ruby #rails #queue #rubyonrails #activerecord #poland #37signals #backgroundprocessing #backgroundprocesses #sidekiq
Anybody know what gotify.fedilab.app is?
It constantly puts dead entries in our #sidekiq morgue.
Add one more vote for using #jemalloc for #rails applications. This is our memory graph for the #Sidekiq workers.
Besides adding the linked buildpack and setting configuration options, we had nothing else to do.
https://elements.heroku.com/buildpacks/gaffneyc/heroku-buildpack-jemalloc
Een "achilleshiel" van #mastodon is het onderdeel #Sidekiq
Als die vast loopt dan komt Mastodon (na een tijdje) krakend tot stilstand (en krijg ik dus ook geen "mention" binnen.
Wanneer je dan zelf even niet op Mastodon kijkt.... dan ben je blij wanneer een gebruiker even een admin-mail stuurt!
De hobbel is geslecht en het leeft allemaal weet (het e.a. moet wel weer opstarten, dus het kan even wat trager zijn)
So You Want To Remove The GVL?, by @byroot
https://byroot.github.io/ruby/performance/2025/01/29/so-you-want-to-remove-the-gvl.html
> For quite a long time, it has been said that Rails applications are mostly IO-bound, hence #Ruby’s #GVL isn’t that big of a deal and that has influenced the design of some cornerstone pieces of Ruby infrastructure like #Puma and #Sidekiq. Regardless, the existence of the GVL still requires these threaded systems to use fork(2) in order to exploit all the cores of a server: one process per core.
We Open-sourced a #Sidekiq extension called `sidekiq-disposal` - it allows you to mark jobs to be killed/discarded by Job ID, Batch ID, or Job Class. We extracted this out of our monolith. I hope to add a UI (into Sidekiq's admin UI). And I'm also looking for a way to do the kill/dispose right in the server middleware, so you don't have to add any custom code to your `sidekiq_retry_in` block.
My #RubyConf talk video is now live!
Die automatische Skalierung von #Sidekiq funktioniert inzwischen ganz gut: gestern Abend hat irgendjemand etwa 3500 Posts auf einmal gelöscht, und obwohl das eine ganze Lawine an ActivityPub-Nachrichten auslöst, gab es keine Verzögerung länger als 74 Sekunden.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst