Re: Some performance notes



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.

It might make sense to limit framerate somehow so at least on really
fast machines you would not eat 100% cpu...

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

Agreed.
								Pavel

-- 
The best software in life is free (not shareware)!		Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]