suvayu ali wrote:
> On Sat, Mar 5, 2011 at 5:23 PM, Bill Davidsen<davidsen@xxxxxxx> wrote:
>> What are you doing which is taking time? You can put a tool like btime in
>> rc.local to show what the system did during boot, in terms of cpu use and
>> iowait.
>
> I don't know about btime but I have used bootchart before. It
> generates amazingly detailed charts for the entire boot process. All
> you need to do is put init=/sbin/bootchartd in the kernel line and
> once you have booted run 'bootchart<outputfile>' to get the chart.
>
btime is purely a summary, just to let you see (a) if you are io bound (most
cases) and if multiple cores are being utilized.
Example:
partygirl.tmr.com 2.6.27.25-78.2.56.fc9.i686 GNU/Linux
Mon Jan 24 17:54:59 EST 2011
Time to boot 35 sec CPU used 36.09 sec
user 17.50
nice 0.00
system 18.21
int proc 0.38
iowait 9.30
CPU(s) 2
Load avg 1.031
partygirl.tmr.com 2.6.27.25-78.2.56.fc9.i686 GNU/Linux
Mon Mar 7 13:15:47 EST 2011
Time to boot 46 sec CPU used 32.32 sec
user 12.81
nice 0.00
system 19.15
int proc 0.36
iowait 21.21
CPU(s) 2
Load avg 0.703
The "load average" is just the ratio of cpu/real time, just a broad indication
of where the cpu is going.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
