[K12OSN] Re: tuxpaint and others running slow
Mike Heins
k12osn at perusion.com
Wed Oct 26 04:02:01 UTC 2005
Quoting Justin Paulsen (paulsenj at frederic.k12.wi.us):
> top - 10:03:37 up 3 days, 21:42, 2 users, load average: 0.51, 0.41, 0.47
> Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie
> Cpu(s): 11.6% us, 6.3% sy, 0.0% ni, 79.4% id, 0.0% wa, 2.7% hi, 0.0% si
> Mem: 4091532k total, 1381188k used, 2710344k free, 134052k buffers
> Swap: 2031608k total, 0k used, 2031608k free, 756124k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 6724 elem_14 11 -4 19480 5984 2336 S 1.7 0.1 0:09.72 tuxtype2
> 6688 elem_03 11 -4 19392 5908 2336 S 1.3 0.1 0:13.09 tuxtype2
> 6706 elem_09 11 -4 19428 5884 2332 S 1.3 0.1 0:12.02 tuxtype2
> 6712 elem_10 11 -4 19428 5884 2332 S 1.3 0.1 0:11.27 tuxtype2
> 6718 elem_12 11 -4 19416 5980 2336 S 1.3 0.1 0:09.99 tuxtype2
> 6679 elem_01 11 -4 19396 5980 2332 S 1.0 0.1 0:15.27 tuxtype2
> 6682 elem_02 11 -4 19396 5984 2336 S 1.0 0.1 0:14.67 tuxtype2
> 6691 elem_04 11 -4 19476 5984 2336 S 1.0 0.1 0:13.40 tuxtype2
> 6694 elem_05 11 -4 19412 5976 2336 S 1.0 0.1 0:13.05 tuxtype2
> 6697 elem_06 11 -4 19412 5980 2340 S 1.0 0.1 0:12.55 tuxtype2
> 6700 elem_07 11 -4 19476 5984 2336 S 1.0 0.1 0:12.29 tuxtype2
> 6703 elem_08 11 -4 19476 5984 2336 S 1.0 0.1 0:10.87 tuxtype2
> 6715 elem_11 11 -4 19476 5984 2336 S 1.0 0.1 0:09.96 tuxtype2
> 6721 elem_13 11 -4 19412 5968 2336 S 1.0 0.1 0:09.16 tuxtype2
> 6730 elem_15 11 -4 19428 5896 2336 S 0.7 0.1 0:07.48 tuxtype2
> 5708 elem_07 15 0 20292 9116 5856 S 0.3 0.2 0:00.48 xfce4-panel
> 6794 root 16 0 2248 1112 800 R 0.3 0.0 0:00.07 top
>
>
> [root at Ayumi ~]# ping -c 100 192.168.0.254
> PING 192.168.0.254 (192.168.0.254) 56(84) bytes of data.
> 64 bytes from 192.168.0.254: icmp_seq=0 ttl=64 time=0.039 ms
> 64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=0.033 ms
> 64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=0.036 ms
> 64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=0.054 ms
> 64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=0.035 ms
> 64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=0.033 ms
> 64 bytes from 192.168.0.254: icmp_seq=6 ttl=64 time=0.035 ms
> 64 bytes from 192.168.0.254: icmp_seq=7 ttl=64 time=0.036 ms
> 64 bytes from 192.168.0.254: icmp_seq=8 ttl=64 time=0.034 ms
> 64 bytes from 192.168.0.254: icmp_seq=9 ttl=64 time=0.035 ms
> 64 bytes from 192.168.0.254: icmp_seq=10 ttl=64 time=0.033 ms
>
You need to run vmstat so that we can see your I/O traffic. Nothing
you show indicates a problem, so my guess is that you have an I/O
hotspot. This is the type of thing I see with poor RAID subsystems
when there are too many queued writes on a system.
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.765.647.1295 tollfree 800-949-1889 <mike at perusion.com>
I am a great believer in luck, and I find that the harder I work
the more luck I have. -- Thomas Jefferson
More information about the K12OSN
mailing list