** Description changed:
- Double-buffered compositing performance is poor.
+ Double-buffered compositing performance is sometimes artificially poor
+ on some intel systems. When this happens the frame rate seen is halved -
+ about 30 FPS. However at the same time, Mir is observed to use very
+
I wonder if calling gbm_surface_lock_front_buffer() a bit earlier would
keep the system sufficiently awake to avoid this?...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Confirmed by duplicate. kdub is seeing similar.
** Changed in: mir
Status: Incomplete = Confirmed
** Changed in: mesa (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can't reproduce this any more.
Mir now has double buffered clients as well as double buffered
compositing so the bug should be more visible, not less. Although vivid
also just got updated to Mesa 10.5 which is where I would expect a fix
to come from. Seems to be fixed, probably by recent
** Branch unlinked: lp:~vanvugt/mir/mesa-double
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is very poor (30 FPS) on intel
To manage
Not work in progress any more.
I think the proposed branch is the final one but we need the more
significant performance bug 1395421 fixed first.
** Changed in: mir
Status: In Progress = Triaged
** Changed in: mir
Milestone: 0.10.0 = None
--
You received this bug notification
** Summary changed:
- Double-buffered compositing performance is very poor (30 FPS)
+ Double-buffered compositing performance is very poor (30 FPS) on intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
