Re: Enable accessibility by default in development releases?

[John Rice <John Rice Sun COM>]

As can sometimes be the case with automated benchmarks, not quite what it seems :(

Derek had an issue with doing one of the automated benchmarks in gnome-terminal and gedit, so he went back and rechecked them all manually. Difference from previous automated results below, when cat'ing a large file in GT or opening a large file in GEdit.

Looks like if you need to cat large files flick the off button :) Apart from that things look ok for enabling this by default. All the previous automated benchmark tests were uneffected.

JR

Revised results from manually measuring;

o cat a big file in gnome-terminal (Using a .html file, 26,332,850 bytes)
-  AllY Off: 40 secs
-  AllY On: 214 secs  (over 500% increase in mean scroll time)

o open a file in gedit (same .html file as above)
-  AllY Off: 3.18 sec
-  AllY On:  4.49 sec  (40% increase in mean file load time)

Federico Mena Quintero wrote:

On Mon, 2005-11-21 at 16:34 +0000, John Rice wrote:

  

Doing 'cat' of a big file in gnome-terminal was the only area where a
significant difference was seen. Approx 45 secs with A11Y ON, and 42.4
secs with A11Y Off.

All other areas looked at above were not significantly different
comparing A11Y On Vs A11Y Off.
    

This is great news :)  And the difference in gnome-terminal could be
just noise.

So, have people *felt* a performance impact from running their session
with a11y enabled, or is it just a placebo?

Anyway, let's go ahead with the change - this will let us test the code
better.

  Federico

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list