On Fri, 2007-08-10 at 07:50 +0200, Nicu Buculei wrote: > Martin Sourada wrote: > It's been a while since I changed my default theme to Nokoda and it > seems fine. > It possible to get some hard numbers, to see how it stand > performance-wise compared with the current theme? Not sure what can be > used here, maybe GtkPerf [1] which is not packaged in Fedora. > > [1] - http://gtkperf.sourceforge.net/ > Hm... two years old app, yet it compiles and installs OK. In case you are interested, there are the results: with Nodoka: GtkEntry - time: 0.10 GtkComboBox - time: 3.00 GtkComboBoxEntry - time: 2.52 GtkSpinButton - time: 0.55 GtkProgressBar - time: 0.14 GtkToggleButton - time: 0.98 GtkCheckButton - time: 0.70 GtkRadioButton - time: 1.06 GtkTextView - Add text - time: 2.12 GtkTextView - Scroll - time: 0.78 GtkDrawingArea - Lines - time: 1.30 GtkDrawingArea - Circles - time: 2.56 GtkDrawingArea - Text - time: 2.97 GtkDrawingArea - Pixbufs - time: 0.25 --- Total time: 19.03 With Clearlooks: GtkEntry - time: 0.10 GtkComboBox - time: 2.99 GtkComboBoxEntry - time: 2.53 GtkSpinButton - time: 0.52 GtkProgressBar - time: 0.56 GtkToggleButton - time: 0.95 GtkCheckButton - time: 0.86 GtkRadioButton - time: 1.15 GtkTextView - Add text - time: 2.16 GtkTextView - Scroll - time: 0.69 GtkDrawingArea - Lines - time: 1.39 GtkDrawingArea - Circles - time: 2.56 GtkDrawingArea - Text - time: 2.92 GtkDrawingArea - Pixbufs - time: 0.25 --- Total time: 19.65 I personally think that the results for the widgets are rather same (i.e. difference is so small that it can taken as statistical error), only progressbar, checkbutton and radiobutton results are noticeably better (probably a result of optimisations I've done to it while testing it with gtk-theme-torturer)... The part from GTKTextView and GTKDrawingArea shouldn't be dependent much on the theme (I think, after seeing what it actually does during those tests...) I tested it previously (when I was on the vacations) with gtk-theme-torturer and did some optimisations back then so the Nodoka is generally faster than clearlooks, only in some areas it is slower. I however have no idea what most of those testing areas ( Boot-create, Boot-map, Boot-expose, Boot-destroy, Expose, Resize) mean... Nodoka usually falls behind Clearlooks in Boot-expose and Expose, while in Boot-map, Boot-destroy and Resize it's faster. In Boot-create it's mostly the same. I can maybe try to summarise the data and publish them in some 'form', but it's quite a lot data, so the graphs I tried so far aren't illustrative enough. I'll probably publish the results no sooner than we release 0.6 beta, as we expect to do further optimisations till then. Martin
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Fedora-art-list mailing list Fedora-art-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-art-list
