[regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough
Bug #1651638 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Kevin DuBois | ||
0.25 |
Triaged
|
Medium
|
Unassigned | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency than interval 1 nested fullscreen clients.
I've reproduced this a couple of times and it is concerning:
Mir 0.25:
Interval 0: 81ms <-- regression
Interval 1: 64ms <-- improvement
Mir 0.24:
Interval 0: 70ms
Interval 1: 96ms
It's the obvious green spike in this chart:
https:/
Although this regression appears to be resolved in the 0.26 series (lp:mir) it's serious enough that we should look into finding what the cause was so that Mir 0.25.1 can get the same fix.
description: | updated |
tags: | added: nested |
summary: |
- [regression] Nested passthrough made latency for interval 0 clients - higher + [regression] Nested passthrough made latency for fullscreen interval 0 + clients (e.g. games and benchmarks) higher |
summary: |
[regression] Nested passthrough made latency for fullscreen interval 0 - clients (e.g. games and benchmarks) higher + clients (e.g. games and benchmarks) higher than without nested + passthrough |
summary: |
- [regression] Nested passthrough made latency for fullscreen interval 0 - clients (e.g. games and benchmarks) higher than without nested - passthrough + [regression] Latency for fullscreen interval 0 clients (e.g. games and + benchmarks) increased with the introduction of nested passthrough |
description: | updated |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm particularly concerned because this suggests series 0.25 has messed up the mailbox dropping algorithm somehow (again).