3 ms·
Maybe a knee jerk reaction, but why cannot the low latency users skip the queue, or even throw out a existing job and reschedule it for later - the bulk users d
by hoppla 4y ago
Maybe a knee jerk reaction, but why cannot the low latency users skip the queue, or even throw out a existing job and reschedule it for later - the bulk users does not care, right?
The problem reminds me how we made a lousy internet connection usable across a whole dorm using queues in m0n0wall to prioritize low latency traffic
- notacoward 4y agoQoS approaches like this are very well studied and very useful, but still have limits. The queuing itself consumes resources and throughput-domain requests that are already in flight will still contend with latency-domain requests (unless you want to implement preemption which is usually very difficult in a system not originally designed for it and also leads to further resource waste). If you want really low latency you have to be completely isolated from the throughput domain.