Originally Posted by
RipTheWorld
Nope, wasn't paging that much if at all. Once I had put more memory in the system (upto 2GB) there was always a minimum of 600MB free, should only start paging if there isn't enough RAM left. The processes seem to take on average 10-15MB each. The CDGrab processes take up a lot more ~150MB each (5x 150MB = 750MB!). Still there is some real conflicts going on somewhere, do they share a lock file maybe?
I don't see why disc I/O should really be a problem either. If the tracks are ripped into RAM then the only disk I/O should be straight to the hard drive. Bandwidth from the DVD Drives is definitely not a problem, you need something like 10+ DVD Drives before you will start worrying the I/O bandwidth (assuming your not using IDE of course). That may obviously be a little different for secure rips though. As for encoded files being written to disk if they are being encoded out of RAM to a single SATAII hard drive then it should happily cope with at least 8-9 lossless file writes.
Like I said this system can throughput 100 CDs/hour normally. This is reduced to about 85 CDS/hour for lossless, but this is more due to CPU constraints (even though it is a Quad Core overclocked to 2.75GHz).
I do know how these programs work as when I first started nearly 4 years ago I wrote my own software. Unfortunately this was on linux and therefore didn't have the codec support which is why I switched to alternative software based on windows (and also for ease of management and access to alternative Meta Data sources). Just trying to help as I think this program has real potential.