Migrating to Solid Queue #93
Replies: 1 comment
-
Hi, I'm reluctant to initially switch to it but I think maybe long term it could be ok. ConcernsPerformanceBasecamp and Hey have tested Solid Queue but they have dedicated hardware with some of the best NVME SSD drives you can get. Most general purpose VPS (DigitalOcean, etc.) have no where near that disk performance. I'd like to how see Solid Queue performs on a real app with a low end VPS where Postgres is doing everything (SQL, cache, queue and action cable). SimplicityGiven we're using Docker Compose, we already have Redis up and running with zero hassle. There's no real complexity decompression for dropping Redis with this project. StabilitySidekiq has been run through the ringer for over a decade. Solid Queue is basically brand new. I'm sure there's rough edges and that's not to put down the team working on it. It's just the reality of any software project. Sidekiq has been used on tons of projects. Long term wins of switching to Solid Queue
Overall I want to switch but I'm not comfortable with it yet, especially if you plan to stick with Postgres. It seems like Good Job is more performant because it uses Postgres specific DB features that don't exist in MySQL or SQLite but Solid Queue wants to remain compatible with all 3 DBs so unless a drastic change is made with Solid Queue it may always be slower than Good Job. The question there is, is it "fast enough"? I'm not sure yet, it's possible. I'd like to see an extensive set of real world benchmarks be done on a low end VPS between all 3 solutions, or at least Solid Queue vs Sidekiq. |
Beta Was this translation helpful? Give feedback.
-
What do you think about moving to the new rails 8 solid queue? Moving away from sidekiq?
Beta Was this translation helpful? Give feedback.
All reactions