Re: Some performance notes

[Owen Taylor <otaylor redhat com>]

Pavel Machek <pavel ucw cz> writes:

> Hi!
> 
> > Generally, on my tests on a 400mhz celeron I felt fairly good about
> > the overall performance with debugging off. Opaque resizing was a
> > little more sluggish than I would like, but other operations seemed
> > pretty snappy, and it would definitely have been useable on a slower
> > machine.
> 
> Note that this is pretty bad. Eating 100% cpu of 400MHz celeron for GUI
> is not too good. You should eat 10%... [win95 was usable on 386/40, 4MB]

Errr, we aren't talking about just sitting there. We are talking
about opaque resizing. Slower machine == 100% cpu at lower framerate.

And if you have a slow machine, then you shouldn't be using opaque
resizing.

And no, GTK+-2.0 isn't going to be useable on a 386/40. (Frankly,
I don't really think Win95 was that pleasant either on such a
machine running real apps.)

There are tradeoffs between the feature set, the ease of programming
and speed, and I have no intention of making that tradeoff
based on machines that have been obsolete for a decade.

> Also take a look at memory being allocated. It tends to be more important
> than cpu cycles. Booting with mem=32M might be nice start.

Booting with mem=32M tells you nothing unless you are testing
an entire environment.

Regards,
                                        Owen