Hi!
> > But then you probably won't be using this switch any more. ;-)
>
> I will when the async i/o support comes in 2.6.19.
>
> > I think it would be better to make it possible to compile out the
> > benchmarking code.
>
> Maybe eventually. Right now, the impact of various combinations of image
> size, compression, early writeout, etc. seems to be poorly understood. I
> think for a while at least it would be a good thing to encourage
> some benchmarks.
>
> Another idea would be to have, say, a 1- or 2-second pause rather than
> waiting for keypress; enough for people to see the output. Then there
> could be a setting to skip the pause.
If you want to do it _right_, write timing info onto disk, then read
it from there. That will not slow the user down, while still telling
them nice statistics when resume is done. Hmmm?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
