← Back to context Comment by klysm 3 years ago Not all use cases are high throughput. That’s not what makes it a toy 4 comments klysm Reply paulddraper 3 years ago "Toy/low throughput" = "Toy or low throughout" djur 3 years ago Can you define "low throughput"? I think people have significantly different ideas of what that means. paulddraper 3 years ago > Can you define "low throughput"?IDK maybe <1000 messages per minuteNot saying SKIP LOCKED can't work with that many. But you'll probably want to do something with lower overhead.FWIW, Que uses advisory locks [1][1] https://github.com/que-rb/que klysm 3 years ago Yeah I think people generally reach for “big” tools when this “toy” would work fine for the vast majority of projects.
paulddraper 3 years ago "Toy/low throughput" = "Toy or low throughout" djur 3 years ago Can you define "low throughput"? I think people have significantly different ideas of what that means. paulddraper 3 years ago > Can you define "low throughput"?IDK maybe <1000 messages per minuteNot saying SKIP LOCKED can't work with that many. But you'll probably want to do something with lower overhead.FWIW, Que uses advisory locks [1][1] https://github.com/que-rb/que klysm 3 years ago Yeah I think people generally reach for “big” tools when this “toy” would work fine for the vast majority of projects.
djur 3 years ago Can you define "low throughput"? I think people have significantly different ideas of what that means. paulddraper 3 years ago > Can you define "low throughput"?IDK maybe <1000 messages per minuteNot saying SKIP LOCKED can't work with that many. But you'll probably want to do something with lower overhead.FWIW, Que uses advisory locks [1][1] https://github.com/que-rb/que klysm 3 years ago Yeah I think people generally reach for “big” tools when this “toy” would work fine for the vast majority of projects.
paulddraper 3 years ago > Can you define "low throughput"?IDK maybe <1000 messages per minuteNot saying SKIP LOCKED can't work with that many. But you'll probably want to do something with lower overhead.FWIW, Que uses advisory locks [1][1] https://github.com/que-rb/que
klysm 3 years ago Yeah I think people generally reach for “big” tools when this “toy” would work fine for the vast majority of projects.
"Toy/low throughput" = "Toy or low throughout"
Can you define "low throughput"? I think people have significantly different ideas of what that means.
> Can you define "low throughput"?
IDK maybe <1000 messages per minute
Not saying SKIP LOCKED can't work with that many. But you'll probably want to do something with lower overhead.
FWIW, Que uses advisory locks [1]
[1] https://github.com/que-rb/que
Yeah I think people generally reach for “big” tools when this “toy” would work fine for the vast majority of projects.