I've recently begun to have trouble with the Linux system that is my amanda server...when amdump runs, the load spikes to between 4.00 and 6.00, and the system becomes nearly unresponsive for the dur
As you are using gzip, is it with the "best" or the "fast" option? The latter uses MANY fewer cpu cycles. -- Jon H. LaBadie jon AT jgcomp DOT com JG Computing 4455 Province Line Road (609) 252-0159 P
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Sun, 23 Nov 2003 23:23:29 -0500
FWIW, of those DLE's that use gzip here, this was true in the later 2.4 kernels. ATM, I'm running 2.6.0-test9-mm5 with the deadline scheduler enabled in this boot, and the machine remains very respon
Author: Eric Siegerman <erics AT telepres DOT com>
Date: Mon, 24 Nov 2003 22:48:43 -0500
Are you short of RAM? If the system's paging heavily, that'd make it crawl too. Not surprising. Recall that Amanda runs client/server even when backing up the server's DLE's. The client-side processe
No, the box has plenty of ram. I realized that about a second after I hit send. However, the more that I look at it, I doubt that 'renice'ing tar and gzip will help--the box seems to have hard drive
Author: Brian Cuttler <brian AT wadsworth DOT org>
Date: Tue, 25 Nov 2003 15:53:43 -0500 (EST)
I'd expect I/O contention to force lower CPU usage... Rather I'd look at the inparallel parameters or the use of the spindle id number in the disklist (optional 4th field) to force single threading a
Author: Brian Cuttler <brian AT wadsworth DOT org>
Date: Tue, 25 Nov 2003 16:03:03 -0500 (EST)
Speaking of disk I/O... VMS (yes, I always resort to that) has a parameter (settable at both the system level and the user level) that determins the min number of clusters/blocks that are allocated t