Hi!
> > "It is an option, so it is not important to get it right" is ugly. It
> > would be nice to actually benchmark this,
>
> Agreed.
>
> > and hardcode the option that provides acceptable performance...
>
> That would be difficult, because it changes substantially from one machine
> to another (depends on the CPU speed, hard disk speed etc.).
Well, our task is "write image to disk, as fast as possible". That
should be doable, no?
> But I think it only is useful with splash, isn't it? If so, we can hardcode
> something reasonable that will be used if splash_param is set and
> won't be used at all otherwise.
Hmm.. we can probably do that. Is smoothly-running progressbar really
all that important?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Suspend-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/suspend-devel