On Mon, Apr 09, 2007 at 06:35:39PM -0600, Eric W. Biederman wrote: > Robin Holt <[EMAIL PROTECTED]> writes: > > > OK. I just got the OK from management. The system we were booting was > > for research only. We had NR_CPUS=num_online_cpus()=4096 which were > > non-hyperthreaded. With no attached I/O and the tweak I originally > > posted plus one change Jack has already gotten accepted, the machine > > booted in approx 12 minutes. > > How much of that time was between the time the kernel was loaded > and before user space was started?
I am scrambling for my timed boot logs. All I am finding right now are boots from 512p machines. For that machine, it took 178 seconds to get to mounting the root filesystem and 75 seconds to get to the login prompt. Of that 75 seconds, 24 was because an NFS server was down and 14 was due to PBS taking time to start. 68.994913| Memory: 2074872032k/2082172528k available (9785k code, 7319136k reserved, 5228k data, 672k init) 36.566117| migration_cost=3869,61218,76048 24.074113| mount: RPC: Remote system error - No route to host 13.972892| PBS mom Those are the long standouts. There are quite a few lines in the boot output which take 2 seconds or less, but none of those are too surprising. Plain and simply, booting that large of a machine has always taken considerable time. The first time we booted a 512p, it took nearly an hour, now that is down to 8 or 9 minutes. > > Twelve minutes sounds like a long time for a boot, if you aren't fsck'ing > filesystems. Not fsck'ing filesystems (xfs). One of the NFS servers that was specified in /etc/fstab was missing, but that is unimportant. Thanks, Robin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/