catch limited bandwidth issues sooner
|Reported by:||Antoine Martin||Owned by:||Antoine Martin|
Got some logs which show:
window.damage.out_latency.90p : 34 window.damage.out_latency.avg : 44 window.damage.out_latency.cur : 2 window.damage.out_latency.max : 1391 window.damage.out_latency.min : 0
Which means that it takes around 44ms to compress and send the packet out to the network layer, often less.
Except that in some cases it can take 1391ms!!
There is another one, which isn't quite as bad:
window.damage.out_latency.90p : 324 window.damage.out_latency.avg : 119 window.damage.out_latency.cur : 25 window.damage.out_latency.max : 408 window.damage.out_latency.min : 1
At that point the UI became sluggish, about 0.5s behind the actual actions.
Not entirely sure what we should be doing here: by the time the OS is pushing back to us, it is too late already and things will be slow because there isn't enough bandwidth to service us.
Maybe we can watch the "damage out latency" more carefully and immediately increase the batching delay to prevent further degradation?
Change History (13)
comment:9 Changed 7 months ago by
|Milestone:||1.0 → 3.0|