High iowait when copying large files in Linux


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
4 views
Always paid attention to another oddity in the disk system in Linux:
When active drives, e.g. when copying a file (no matter between different disks or not) the CPU usage grows up very much (most of it is in iowait, usually completely focused on one core) and the system subjectively begins to work more slowly, becomes less responsive.
The winchesters I have SATA2 in the BIOS before there was mode IDE to SATA, recently put AHCI, no difference noticed)
Stone is a dual-core Phenom II x2 555.
Tested hdparm'ω the speed of linear reading — to a new terabaytnye 100 MB/s, for the old screw on 320Gb — 70 MB/s.
I don't know how these values are normal.
A large file copy from the old screw on new — about 50 MB/s.
System is ArchLinux x64.

I would like to hear the opinions of those better versed in working with Linux disks.
by | 4 views

3 Answers

0 like 0 dislike
12309 :-(
by
0 like 0 dislike
This is normal. Do not worry.
by
0 like 0 dislike
If you copy something big from system or for system screw or the screw(s) where is your $HOME, then logically the system will be subjectively slower.
\r
Big iowait — is also a logical thing, it is usually the higher, the more extent-s (read: the more fragmented) files.
\r
I have when copying files on a separate screw, significantly system becomes slower at all.
by
110,608 questions
257,186 answers
0 comments
27,390 users