| 2014-04-17 04:15:19 |
Daniel van Vugt |
bug |
|
|
added bug |
| 2014-04-17 04:16:14 |
Daniel van Vugt |
tags |
performance pm regression-uodate |
performance pm regression-update |
|
| 2014-04-17 04:16:23 |
Daniel van Vugt |
mir: milestone |
|
0.1.9 |
|
| 2014-04-22 06:26:27 |
Daniel van Vugt |
summary |
[regression] Clients skip frames on 40Hz displays |
[regression] Clients skip frames periodically |
|
| 2014-04-22 06:27:41 |
Daniel van Vugt |
description |
I used to have an intel GPU (GM45 with SU9600) which would clock down the refresh rate to 40Hz for power savings. Although I don't have it any more, I can see we probably have broken that use case. Clients will probably skip frames now and look "unsmooth".
I think the simple solution is to ensure the new buffer consumer thread never runs faster than any real display. It should probably be slowed down to about 10Hz. |
Running mir_demo_server_shell with mir_demo_client_egltriangle I see frame skips every 10 seconds or so, which is visible in the output too:
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
OLD DESCRIPTION:
I used to have an intel GPU (GM45 with SU9600) which would clock down the refresh rate to 40Hz for power savings. Although I don't have it any more, I can see we probably have broken that use case. Clients will probably skip frames now and look "unsmooth".
I think the simple solution is to ensure the new buffer consumer thread never runs faster than any real display. It should probably be slowed down to about 10Hz. |
|
| 2014-04-22 06:27:44 |
Daniel van Vugt |
mir: importance |
Medium |
High |
|
| 2014-04-22 06:27:48 |
Daniel van Vugt |
mir: status |
New |
In Progress |
|
| 2014-04-22 06:27:52 |
Daniel van Vugt |
mir: assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2014-04-22 06:29:32 |
Daniel van Vugt |
summary |
[regression] Clients skip frames periodically |
[regression] Client judders, skipping frames periodically |
|
| 2014-04-22 09:42:51 |
Daniel van Vugt |
branch linked |
|
lp:~vanvugt/mir/judder |
|
| 2014-04-23 07:09:09 |
Daniel van Vugt |
description |
Running mir_demo_server_shell with mir_demo_client_egltriangle I see frame skips every 10 seconds or so, which is visible in the output too:
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
OLD DESCRIPTION:
I used to have an intel GPU (GM45 with SU9600) which would clock down the refresh rate to 40Hz for power savings. Although I don't have it any more, I can see we probably have broken that use case. Clients will probably skip frames now and look "unsmooth".
I think the simple solution is to ensure the new buffer consumer thread never runs faster than any real display. It should probably be slowed down to about 10Hz. |
Running mir_demo_server_shell with mir_demo_client_egltriangle I see frame skips every 10 seconds or so, which is visible in the output too:
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
60 FPS
59 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
60 FPS
61 FPS
This only seems to happen when a single monitor is plugged in.
OLD DESCRIPTION:
I used to have an intel GPU (GM45 with SU9600) which would clock down the refresh rate to 40Hz for power savings. Although I don't have it any more, I can see we probably have broken that use case. Clients will probably skip frames now and look "unsmooth".
I think the simple solution is to ensure the new buffer consumer thread never runs faster than any real display. It should probably be slowed down to about 10Hz. |
|
| 2014-04-23 07:18:25 |
Daniel van Vugt |
branch linked |
|
lp:~raof/mir/1hz-rendering-always |
|
| 2014-04-23 07:52:44 |
Daniel van Vugt |
branch linked |
|
lp:~afrantzis/mir/consume-only-not-rendered-buffers |
|
| 2014-04-24 18:04:04 |
kevin gunn |
summary |
[regression] Client judders, skipping frames periodically |
[regression] [nonblockswap] Client judders, skipping frames periodically |
|
| 2014-04-24 18:04:12 |
kevin gunn |
tags |
performance pm regression-update |
nonblockswap performance pm regression-update |
|
| 2014-04-25 01:38:27 |
kevin gunn |
mir: milestone |
0.1.9 |
0.1.10 |
|
| 2014-04-29 02:35:24 |
Daniel van Vugt |
mir: assignee |
Daniel van Vugt (vanvugt) |
Mir development team (mir-team) |
|
| 2014-05-09 09:39:48 |
Daniel van Vugt |
tags |
nonblockswap performance pm regression-update |
nonblockswap performance pm regression |
|
| 2014-05-21 13:03:07 |
PS Jenkins bot |
mir: status |
In Progress |
Fix Committed |
|
| 2014-05-22 09:36:23 |
Daniel van Vugt |
mir: status |
Fix Committed |
In Progress |
|
| 2014-05-27 09:27:52 |
Daniel van Vugt |
branch linked |
|
lp:~mir-team/mir/10Hz-rendering-always |
|
| 2014-05-29 14:28:41 |
Cemil Azizoglu |
mir: milestone |
0.2.0 |
0.3.0 |
|
| 2014-06-03 17:49:51 |
PS Jenkins bot |
mir: status |
In Progress |
Fix Committed |
|
| 2014-06-19 02:33:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/utopic-proposed/mir |
|
| 2014-06-19 02:41:13 |
Launchpad Janitor |
mir (Ubuntu): status |
New |
Fix Released |
|
| 2014-06-20 11:08:24 |
kevin gunn |
mir: status |
Fix Committed |
Fix Released |
|
| 2014-07-01 07:44:24 |
Daniel van Vugt |
mir (Ubuntu): importance |
Undecided |
High |
|
