My test is to throttle the bandwith using "rsync --bwlimit=<throughput>"
I am testing using vmware on /images3.
Vmware runs fluent until I copy a lot (7Gig vmdk-file) to /images3, which
is a separat harddrive on which 5 vmware systems are having their .vmdk-files.
Copying this 7Gig file freezes the vmware systems for > 30 seconds.
And now with limited bandwith ...
all jobs run fine, no hangig or else:
rsync --bwlimit=10000 /images5/vmware/vlab03/STD_XP_Prof.vmdk /images3/test
rsync --bwlimit=20000 /images5/vmware/vlab03/STD_XP_Prof.vmdk /images3/test
some jobs start to become slow and hang:
rsync --bwlimit=30000 /images5/vmware/vlab03/STD_XP_Prof.vmdk /images3/test
a lot of jobs hangs and are very slow, some freeze:
rsync --bwlimit=40000 /images5/vmware/vlab03/STD_XP_Prof.vmdk /images3/test
This is my estimation:
rsync is creating more dirt than the "kernel" can get rid off and
the system is put into this "processes are blocked for writes" (see previous posting) mode.
Hi again:
My test is to throttle the bandwith using "rsync --bwlimit= <throughput> "
I am testing using vmware on /images3.
Vmware runs fluent until I copy a lot (7Gig vmdk-file) to /images3, which
is a separat harddrive on which 5 vmware systems are having their .vmdk-files.
Copying this 7Gig file freezes the vmware systems for > 30 seconds.
And now with limited bandwith ...
all jobs run fine, no hangig or else: vmware/ vlab03/ STD_XP_ Prof.vmdk /images3/test vmware/ vlab03/ STD_XP_ Prof.vmdk /images3/test
rsync --bwlimit=10000 /images5/
rsync --bwlimit=20000 /images5/
some jobs start to become slow and hang: vmware/ vlab03/ STD_XP_ Prof.vmdk /images3/test
rsync --bwlimit=30000 /images5/
a lot of jobs hangs and are very slow, some freeze: vmware/ vlab03/ STD_XP_ Prof.vmdk /images3/test
rsync --bwlimit=40000 /images5/
This is my estimation:
rsync is creating more dirt than the "kernel" can get rid off and
the system is put into this "processes are blocked for writes" (see previous posting) mode.
I hope that my input can help.