PgHero VS Sidekiq

I am using https://github.com/ankane/pghero/ and this is one of its features with GUI

I use either PgHero or Rails PG Extras on every project

There are tools available which can look at your Postgres logs and tell you if you need to add indexes, I've used https://github.com/ankane/pghero before and it seems decent.

https://github.com/ankane/pghero (open source equivalent to pganalyze)

- [pghero](https://github.com/ankane/pghero)

pghero

If you are using PostgreSQL you can enable logging of slow queries and connect to the server with pghero (https://github.com/ankane/pghero) and check top queries by the number of requests and total usage time. Also, you can just enable logging of queries in Django, and on each request, you will have a list of queries on development, sometimes it's just a missing select_related of prefetch_related to increase performance, or you need to create a complex index.

If you are using rails, pghero is a great gem to get better visibility on your Postgres performance

https://github.com/ankane/pghero

I know others can answer this better but we use a combination of PgHero and logging of slow queries trough jOOQ.

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.

I'd say Sidekiq is the top competitor here.

There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.

It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594

That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).

Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.

Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.

https://github.com/sidekiq/sidekiq/wiki/Reliability

> I'm not sure feature withholding has traditionally worked out well in the developer space.

I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.

I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.