> Seriously, these benchmarks have nothing to do with anything that > matters... when was the last time your application launch time was > primarily dependent on the WM, or when was the last time you opened 100 > windows all at once and were all DAMMIT WHY DOES MY WM TAKE 1.3 SECONDS > INSTEAD OF 0.7 SECONDS TO FLOOD MY SCREEN IN 100 WINDOWS??? ;-)
Thinking about terminal services: If you accumulate the time spent on things which could be optimized, and cut it in half, you might e.g. accommodate one or two more users on the same terminal server, or might make the terminal server more responsive/kick CPU usage. Time spent in WM code also counts toward this goal. > > But if you want to improve the benchmark anyhow, > http://bugzilla.gnome.org/show_bug.cgi?id=309567 shows one way. It > should speed up some other stuff and clean up the code as well so it > isn't entirely useless. > > Havoc > > > _______________________________________________ > gnome-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-devel-list -- Manuel Amador <[EMAIL PROTECTED]> http://www.amautacorp.com/ +593 (4) 220-7010 _______________________________________________ gnome-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-devel-list
