On Saturday 31 March 2007 10:04, Joe Shaw wrote: > Hi, > > On 3/31/07, Rajko M. <[EMAIL PROTECTED]> wrote: > > It is actually the I/O that is slow and faster CPU doesn't help much. > > Problem is when 2 or more programs are trying to access HD at the same > > time, and that happens on the first boot. > > Indeed. As CPUs get faster, the amount of time applications spend > doing IO approaches 100%.
Yes. To load 1 GB from HD with 50 MB/s is 20s, after that it goes fast, but if there is 2000 files in that 1 GB, which can easily happen, the speed is down. I was wondering why is Knoppix booting faster from CD than from HD, but before above sentence I never tried to think about I/O impact on boot process. Maybe we ^H^H^H :-) you, developers, can consider booting the image in the similar way Knoppix does. Suspend to disk should be the right way, but right now it doesn't work here. I suspect that graphic (nVidia) initialization fails. > Beagle isn't started at boot though; the cron job is started 15 > minutes after the first boot, and the per-user daemon is started > something like 2 or 3 minutes after login (to avoid slowing it down). > So slow boot times (which I agree have gotten worse) have nothing to > do with Beagle. I mentioned that a lot of negative opinions picked up around kept me from giving a test ride to Beagle. > There is some data and analysis on the boot process here: > > http://en.opensuse.org/Boot_time > > In fact, in there I say that a parallel boot process doesn't help much > (and in fact may even hurt us) because most of the time is spend doing > concurrent IO. After this discussion, it seems clear that concurrent access to HD is bad. I'll try to see is it possible to switch to old style in 10.2 and post result on above page. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
