4 ms·
If you want close to real time performance, why go for a task table at all? You can spawn threads and track them instead provided you have the resources. If you
by ivanbakel 2y ago
If you want close to real time performance, why go for a task table at all? You can spawn threads and track them instead provided you have the resources. If you don't have the resources, I don't see why the minor listen/notify overhead would bother you, since tasks will wait some of the time regardless.
- maxbond 2y agoI explain in another comment that I want jobs to be durable, so I can't just spin up a new thread. It's not the performance overhead that bothers me as much as the session-sticky state and additional complexity in the database, my instinct is that it will cause outages in ways that take significant Postgres chops to diagnose and correct. That's just an instinct though, it could be far off base.