High I/O Wait when copying/moving Files
Hi All,
I am currently experiencing a very high IO wait whenever I copy or move a large file from a directory (say /home/user1) to another directory (say /home/user2). WA percentage in top command reaches more than 50%. This disables and hangs the desktop. I read somewhere that during copying of files, large percentage of my memory is used for cache. Is it possible to set a certain amount of my memory (8 Gb) during copy operations? I know cache memory is automatically given back to the system, but I want to allocate specific amount during copy so the Redhat desktop does not experience hang and unresponsiveness.
Responses
Not really giving a lot of information to go on, here. Just to start, some of the things that might be helpful in providing an answer would be:
* What version of Red Hat
* What patch-set has been applied
* What filesystem type (extN, xfs, etc.)
* What filesystem mount-options are in us
* How are you copying files
* How are you moving files
* Is there a performance difference between copying and moving
* Are the source and destination on separate filesystems
* What's the underlying storage look like for the source/destination
* Do you have A/V enabled on your system (e.g., I've seen McAfee absolutely murder performance on both copy and move operations)
Oof... The HTS543232A7A384 is a slow hard drive to begin with (and likely accounts for a significant percentage of your performance issues).
Nautilus can (or at least used to) sometimes cause slower performance than work done at the CLI.
On your system, copying from "/" (hosted on sda3) to "/home" (hosted on sda5) is an operation that crosses filesystems. This means you won't get any kinds of performance improvments to moves that you'd get were you doing a move wholly within "/" or within "/home". That said, such 'same filesystem' performance improvements for moves are often casualties of graphical file-managers like Nautilus (which often implement a copy-then-delete rather than an actual move).
In general, XFS is optimized for large, sequential I/Os associated with streaming media. Its performance can get a bit dodgy when transfering lots of small files from filesystem to filesystem. XFS is particularly dodgy on delete operations ...which may be the real culprit here, as Nautilus may be waiting for the delete operations to complete.
At any rate, were I in your shoes, I'd probably try:
* Patching up the OS
* Try using the CLI to copy and/or move files and see if removing Nautilus from the equation improves things
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
