Skip to contentSkip to conversation

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

DISCUSSION Andreas Hartmann 3 participants 5 messages Apr 4, 2004 – Apr 5, 2004 3 messages 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]

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

#2 lore raw
Quoted 11 lines · Bill Davidsen
Quoted 8 lines · Andreas Hartmann

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.

If the processor and the kernel could do other things during wa, like compiling e.g., it would be no problem. But it seems to be, that this is not possible. Or did I oversee something?

Regards,
Andreas Hartmann

#3 lore raw
Quoted 14 lines · Andreas Hartmann
Quoted 12 lines · Bill Davidsen
Quoted 8 lines · Andreas Hartmann

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

Quoted 6 lines
Quoted 1 line

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.

If the processor and the kernel could do other things during wa, like compiling e.g., it would be no problem. But it seems to be, that this is not possible. Or did I oversee something?

Yes, wio is similar to idle, processor is available for work even if disk access is running slowly.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

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

#5 lore raw
Quoted 8 lines · Mikhail Ramendik

Hello,

Quoted 4 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 !

Quoted 5 lines
Quoted 1 line

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.

Yes. But it's curious:
Take a tar-file, e.g. tar the compiled 2.6 kernel directory. Than, untar it again - the machine behaves total normaly. And the 2.6-kernel is about 23% faster than the 2.4-kernel.

Quoted 4 lines

Yours, Mikhail Ramendik

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

No problem - it's easier to read with comment directly in the text.

Regards,
Andreas Hartmann

#6 lore raw

Hello,

Quoted 7 lines · Andreas Hartmann
Quoted 3 lines

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

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

Yes. But it's curious:
Take a tar-file, e.g. tar the compiled 2.6 kernel directory. Than, untar it again - the machine behaves total normaly.

Not really. I tried a "simple" tar (no gzib/bzip2) - it was the same as with cp, a near-100% CPU "system" load, most of it iowait.

If I use bzip2 with tar, then yes, the load is nearly 100% "user", actually it's bzip2. But this is because the disk i/o is done at a *far* slower rate; the bottleneck is the CPU. If we don't read (or write) the disk heavily, naturally the system/iowait load is low.

I tried doing a "cp" in another xterm window, while the tar/bzip2 was running. And sure enough, up the CPU system/iowait usage goes - the "cp"'s disk i/o takes much of the CPU time away from the bz2 task! Looks exactly like a cause of performance problems.

(All of this was done on 2.6.5-rc3-mm4).

Yours, Mikhail Ramendik

Quoted 16 lines

And the 2.6-kernel is about
23% faster than the 2.4-kernel.

Quoted 4 lines

Yours, Mikhail Ramendik

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

No problem - it's easier to read with comment directly in the text.

Regards,
Andreas Hartmann

#7 lore raw
Quoted 6 lines · Mikhail Ramendik

Hello,

Quoted 2 lines · Andreas Hartmann
Quoted 2 lines

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

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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

Yes. But it's curious:
Take a tar-file, e.g. tar the compiled 2.6 kernel directory. Than, untar it again - the machine behaves total normaly.

Not really. I tried a "simple" tar (no gzib/bzip2) - it was the same as with cp, a near-100% CPU "system" load, most of it iowait.

??? was it in system or wait-io? One or the other, if you can't tell the difference update your tools, see what's really happening.

Quoted 12 lines

If I use bzip2 with tar, then yes, the load is nearly 100% "user", actually it's bzip2. But this is because the disk i/o is done at a *far* slower rate; the bottleneck is the CPU. If we don't read (or write) the disk heavily, naturally the system/iowait load is low.

I tried doing a "cp" in another xterm window, while the tar/bzip2 was running. And sure enough, up the CPU system/iowait usage goes - the "cp"'s disk i/o takes much of the CPU time away from the bz2 task! Looks exactly like a cause of performance problems.

(All of this was done on 2.6.5-rc3-mm4).

Signature · 3 lines
bill davidsen <[email protected]>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979