Results 1 to 6 of 6
Hi,
I don't know if that's the right section of the forum.
While I'm copying big files (or a lot of files) the system gets so slow that it's hardly ...
- 10-25-2009 #1Linux Newbie
- Join Date
- Feb 2009
- Posts
- 100
system slow while copying big files
Hi,
I don't know if that's the right section of the forum.
While I'm copying big files (or a lot of files) the system gets so slow that it's hardly usable. It's a modern laptop with 3GB of RAM. I'm using Slackware 13.
Something must be wrong with my system.
Thanks for any help
- 10-25-2009 #2Linux User
- Join Date
- Jan 2007
- Location
- cleveland
- Posts
- 452
try putting the copy down a little: use "nice"
the sun is new every day (heraclitus)
- 10-26-2009 #3
Probably what is happening is you have maxed out your disk transfer and anything else you try to access from disk will subsequently be slowed severely.
- 10-26-2009 #4Linux Newbie
- Join Date
- Feb 2009
- Posts
- 100
Thanks for your replies.
If that's the maximum my system can reach, fine. I'll have to decrease the priority of copy using nice. I don't mind if it copies slower, as long as I can do other things in the meantime.
I've heard about 'nice' before, I'll need to google some info about it.
- 10-26-2009 #5
You can see if you are IO bound fairly simply.
Open a terminal and execute iostat -d -x 5 and watch output while running your copy. You can also use vmstat 5 and watch the last column, this is iowait time.
- 10-26-2009 #6Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
The same thing happens on my Linux systems when I copy big files around. It basically becomes I/O bound. I have a CentOS 5.4 system with 10 sata drives installed (about 10TB total) and this happens to me when I'm copying a bunch of big files (DVD ISO images for example) as well. I'm not sure there's much you can do about that. I find that if I do the copy externally from the GUI, such as using cp/mv from a command line, that the impact isn't as severe as doing it from the GUI file manager such as konqueror (KDE), so it might not just be an I/O situation as overloading the GUI subsystem as well. FWIW, I have an 8 core system with 8GB RAM and both internal SATA controller as well as a PCI-X esata controller, and neither the CPU nor the RAM are overloaded in these cases. The data moves at maximum disc speed in any case.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote