On 1/10/06,
Petersson, Mats <
mats.petersson@xxxxxxx> wrote:
Gzip
will use up a fair amount of cpu-time, but the time it take to
transfer the image that is 30-70% smaller is significantly more than
the CPU-time it's taken, so unless you have something else productive
to do with your cpu whilst you're backing up/transferring the file(s), you're
probably better off compressing the file(s).
Well my backup server is going to be just sitting on the next rack probably so the network transfer won't affect much. As compared to cpu time, i would rather prefer to use the cpu time for processing inside the domains than for running tar+gzip.
Hmm... given this, one solution would be to run some kind of background process which monitors the cpu usage, when its low, run the backup service, if there is a demand of the cpu by any process/ domain, just pause the backup and resume whenever cpu becomes free. However if the host keeps on being too much busy always the backup process can be hanged up in memory for ages (have seen this myself).
--
regards,
Anand
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users