> if code is written to handle 1 job at a time and needs to make several roundtr... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

dns_snek 6 months ago | parent | context | favorite | on: I’m leaving Redis for SolidQueue

> if code is written to handle 1 job at a time and needs to make several roundtrips to the same db inside the same locking transaction.

Do you mean the application code? The worker itself causing the bottleneck is definitely one possibility however if that were the case the issue wouldn't have resolved itself when they switched to a different job queue.

vjerancrnjak 6 months ago [–]

Well, you would no longer have thousands of open transactions maintaining the locks.

Of course, if q on top of psql is reasonably implemented (lease), what they say makes no sense.

Consider applying for YC's Fall 2026 batch! Applications are open till July 27.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact