<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
</div>Ok, that seems sufficient, thanks.<br>
<br>
For a bonus, could you still explain what this FPS count actually<br>
measures?<br>
<br>
Something like this: it measures how often a very simple GL program<br>
can show new content. This is limited by the monitors' refresh<br>
rates, system load, compositor performance, and finally the<br>
program's own performance.<br>
<br>
"show new content" is a hint, that it does not measure rendering<br>
speed nor "Wayland speed".<br>
<br>
I wrote monitors in plural, because having the gears surface on<br>
multiple monitors simultaneously might limit the FPS to the sum of<br>
the individual refresh rates, depending a bit. I'm not sure how<br>
Weston behaves currently.<br>
<br>
Heh, that would be a nice headline: "Adding more monitors in clone<br>
mode speeds up Wayland!" ;-)<br>
<br>
<br>
Thanks,<br>
pq<br><br></blockquote><div><br>This message is indeed very important as many users get confused very easily, thinking that the popular 'gears' implementation is a direct measure of their graphics drivers and/or system/platform performance. This is clearly not the case and the message should reflect that, while explaining what these numbers actually mean.<br>
<br><br>Scott <br></div></div><br>