24 ms·
Your conclusions about latency, and being able to restructure things so tasks are much smaller -- make sense. (Potentially; I'd still want to benchmark my own r
by jrochkind1 13y ago
Your conclusions about latency, and being able to restructure things so tasks are much smaller -- make sense. (Potentially; I'd still want to benchmark my own real world app before assuming!)
(I am confused with your first paragraph and a half, I think you have some typos in there, or I just don't understand what you're saying. But I understand what you're saying about latency and about being able to restructure tasks to be smaller, thanks.)
- benmanns 13y agoAck, sorry for the confusion. I mean that if your users are waiting on jobs, they get the result when `encode time` + `enqueue time` + `wait time` + `dequeue time` + `decode time` + `execute time` is completed. Even though you might not need raw 1000 jobs/second throughput, your users will still benefit by reducing `wait time` + `dequeue time` + `decode time`, which goworker does.