* kernel performance issue
@ 2008-07-31 10:38 richard
0 siblings, 0 replies; only message in thread
From: richard @ 2008-07-31 10:38 UTC (permalink / raw)
To: linux-kernel; +Cc: torvalds, akpm
Hi:
I have a question about the kernel performance of kernel 2.6.24. I use
"time"
to account the time cost of "date" execution, and find that the "real time"
of kernel 2.6.24 is always bigger than kernel 2.6.21 on my arm board.
For my
understanding, the time cost of 2.6.24 shouldn't be bigger than 2.6.21,
because
it is a upgrade of 2.6.21 and the its performance should be better than
2.6.21,
if I am wrong please let me know.
[root@Linux /root]#cat ./date-loop.sh
#! /bin/sh
loop=1
while [ $loop -le 50 ]
do
date +%s
loop=$(($loop+1))
done
Time cost in kernel 2.6.24:
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.06s
sys 0m 0.43s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.07s
sys 0m 0.42s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.09s
sys 0m 0.40s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.07s
sys 0m 0.41s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.07s
sys 0m 0.42s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.09s
sys 0m 0.40s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.06s
sys 0m 0.43s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.08s
sys 0m 0.41s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.09s
sys 0m 0.40s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.10s
sys 0m 0.39s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.05s
sys 0m 0.44s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.05s
sys 0m 0.44s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.09s
sys 0m 0.40s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.07s
sys 0m 0.42s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.07s
sys 0m 0.42s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.48s
user 0m 0.09s
sys 0m 0.40s
[root@Linux /root]#
Time cost in kernel 2.6.21:
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.08s
sys 0m 0.38s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.07s
sys 0m 0.39s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.08s
sys 0m 0.38s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.06s
sys 0m 0.40s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.10s
sys 0m 0.36s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.04s
sys 0m 0.42s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.07s
sys 0m 0.39s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.08s
sys 0m 0.38s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.10s
sys 0m 0.36s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.09s
sys 0m 0.37s
[root@Linux /root]#time ./date-loop.sh > /dev/null
real 0m 0.45s
user 0m 0.07s
sys 0m 0.39s
[root@Linux /root]#
--
Best Regards,
Yang Lu
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-31 10:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-31 10:38 kernel performance issue richard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox