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

Re: boot sequence of a Debian/unstable system



Jochen Voss wrote:
> The most plausible candidates during seconds 3-5 for further
> optimisation might be the depmod call and the 3 seconds sleep caused
> by the /etc/rcS.d/S4...  (name truncated) script from seconds 8 to 10.

That script would be hotplug.

> 1) Either the top output format changed between sarge and sid, or
>   it is other influences.  Your data did not include the I/O wait times,
>   so they are omitted in the diagram.  My top headers look like this:
> 
>    top - 12:55:35 up 0 min,  0 users,  load average: 0.15, 0.03, 0.01
>    Tasks:  19 total,   2 running,  17 sleeping,   0 stopped,   0 zombie
>    Cpu(s):  2.0% us,  8.6% sy,  0.0% ni, 65.6% id, 23.8% wa,  0.0% hi,  0.0% si
> 
>   while yours look are
> 
>    top - 20:09:54 up 0 min,  0 users,  load average: 0.00, 0.00, 0.00
>    Tasks:  12 total,   1 running,  11 sleeping,   0 stopped,   0 zombie
>    Cpu(s):   6.9% user,  10.9% system,   0.0% nice,  82.3% idle

This seems to be a difference between the 2.4 and 2.6 kernel. I use a
2.4 kernel on that machine because some installer bugs prevent the 2.6
kernel from installing.

> 2) Top has this annoying habit of truncating the output according to the
>   screen width.  Yours seems to be 80 columns which causes some of the
>   process names to be truncated. 

Probably COLUMNS=100 would work around this.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: