Skip to contentSkip to conversation

2.6.4 : 100% CPU use on EIDE disk operarion, VIA chipset

DISCUSSION Andreas Hartmann 3 participants 4 messages Apr 3, 2004 – Apr 4, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 11 lines · Mikhail Ramendik

Hello,

I have an computer with an AMD Duron, and the motehrboard chipset is VIA KT133. The hard drive is a Seagate Barracuda 7200.7 ; no other EIDE devices are attached.

I run an RH9-based distro, and added a 2.6.4 kernel to it. The following problem was tested with two kernel variants: 2.6.4+wolk2/0 with preeemption enabled, and 2.6.4 plain from kernel.org with preemption disabled. No difference.

Quoted 7 lines

I noticed performance problems with 2.6.4, and tracked them to strange HDD behavior.

It turned out that on disk-intensive operation, the "system" CPU usage skyrockets. With a mere "cp" of a large file to the same direstory (tested with ext3fs and FAT32 file systems), it is 100% practically all of the time !

Which tool do you use for measure? xosview?

I'm having here the same problem. But it depends on the tool which is used for measuring. If I use top from procps 3.2, I can't see this high system load. "time" can't see it, too.

This is what top says during cp of 512MB-file:
Cpu(s): 2.0% us, 8.3% sy, 0.0% ni, 0.0% id, 89.0% wa, 0.7% hi, 0.0% si

New is "wa", what probably means "wait". This value is very high as long as the HD is writing or reading datas:

cp dummy /dev/null
produces this top-line:
Cpu(s): 3.0% us, 5.3% sy, 0.0% ni, 0.0% id, 91.0% wa, 0.7% hi, 0.0% si

and time says:

real    0m53.195s
user    0m0.013s
sys     0m2.124s

But you're right, 2.6.4 is slower than 2.4.25. See the thread "Very poor performance with 2.6.4" here in the list.

Regards,
Andreas Hartmann

#2 lore raw
Quoted 26 lines · Andreas Hartmann
Quoted 11 lines · Mikhail Ramendik

Hello,

I have an computer with an AMD Duron, and the motehrboard chipset is VIA KT133. The hard drive is a Seagate Barracuda 7200.7 ; no other EIDE devices are attached.

I run an RH9-based distro, and added a 2.6.4 kernel to it. The following problem was tested with two kernel variants: 2.6.4+wolk2/0 with preeemption enabled, and 2.6.4 plain from kernel.org with preemption disabled. No difference.

Quoted 7 lines

I noticed performance problems with 2.6.4, and tracked them to strange HDD behavior.

It turned out that on disk-intensive operation, the "system" CPU usage skyrockets. With a mere "cp" of a large file to the same direstory (tested with ext3fs and FAT32 file systems), it is 100% practically all of the time !

Which tool do you use for measure? xosview?

I'm having here the same problem. But it depends on the tool which is used for measuring. If I use top from procps 3.2, I can't see this high system load. "time" can't see it, too.

Quoted 8 lines

This is what top says during cp of 512MB-file:
Cpu(s): 2.0% us, 8.3% sy, 0.0% ni, 0.0% id, 89.0% wa, 0.7% hi, 0.0% si

New is "wa", what probably means "wait". This value is very high as long as the HD is writing or reading datas:

cp dummy /dev/null
produces this top-line:
Cpu(s): 3.0% us, 5.3% sy, 0.0% ni, 0.0% id, 91.0% wa, 0.7% hi, 0.0% si

Yes "wa" is not intuitive, some other operating systems use "wio" for "wait i/o" time. As noted in the other thread, you can try the deadline elevator or increased readahead for your load.

Quoted 8 lines

and time says:

real    0m53.195s
user    0m0.013s
sys     0m2.124s

But you're right, 2.6.4 is slower than 2.4.25. See the thread "Very poor performance with 2.6.4" here in the list.

Much discussed, not overly fixed :-(

Signature · 3 lines
bill davidsen <[email protected]>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979
#3 lore raw
In reply to Andreas Hartmann

Hello,

Quoted 6 lines · Andreas Hartmann
Quoted 4 lines

It turned out that on disk-intensive operation, the "system" CPU usage skyrockets. With a mere "cp" of a large file to the same direstory (tested with ext3fs and FAT32 file systems), it is 100% practically all of the time !

Which tool do you use for measure? xosview?

IceWM's monitor. (It just runs all the time, that's how I spotted the problem).

Quoted 6 lines

I'm having here the same problem. But it depends on the tool which is used for measuring. If I use top from procps 3.2, I can't see this high system load. "time" can't see it, too.

This is what top says during cp of 512MB-file:
Cpu(s): 2.0% us, 8.3% sy, 0.0% ni, 0.0% id, 89.0% wa, 0.7% hi, 0.0% si

I don't have procps 3.2 as yet, will compile it soon; however I think it's the same issue.

I tried the deadline elevator, as suggested by Bill Davidsen down this thread. It did not help. In fact the performance fell (the same file took a longer time to copy); the CPU use is still 100% (with an occasional "dent" or two, but these are very small in duration).

I also tried increasing the read-ahead. It does not help either.

Finally I tried increasing the read-ahead WITH the deadline elevator. The performance rose (compared to the one measured with the standard read-ahead and the deadline elevator). And the CPU load still did not change.

I don't have much CPU to waste (Duron 650 MHz), so I think some performance problems I see are linked to this.

Quoted 2 lines

But you're right, 2.6.4 is slower than 2.4.25. See the thread "Very poor performance with 2.6.4" here in the list.

I've looked at it. I will try the latest rc-mm kernel and report the results.

Yours, Mikhail Ramendik

#4 lore raw
In reply to Andreas Hartmann

Hello,

Quoted 6 lines · Andreas Hartmann
Quoted 4 lines

It turned out that on disk-intensive operation, the "system" CPU usage skyrockets. With a mere "cp" of a large file to the same direstory (tested with ext3fs and FAT32 file systems), it is 100% practically all of the time !

But you're right, 2.6.4 is slower than 2.4.25. See the thread "Very poor performance with 2.6.4" here in the list.

As recommended there, I have tried 2.6.5-rc3-mm4.

No change. Still 100% CPU usage; the performance seems teh same.

Yours, Mikhail Ramendik

P.S. Sorry for making all comments into answers to your letter. I just don't want to break the thread.