Klaus Karcher wrote:
There are correlations between cache multiplier, execution time, probability for reverse cell cache warnings and malloc errors and the number of page faults reported by time -lp (see attachment):
It's very system dependent. I notice for instance that it depends on whether my web browser is open or not (on MSWindows), and the OS doesn't seem to kick it out of memory when Argyll starts paging. The current development code shouldn't fail with a malloc failure, and I will tweak the memory usage targets down a bit to try and reduce the chances of paging (sorry Klaus, that will mess up your numbers!). What I really need is a programatic way of detecting excessive swapping and scaling down the memory usage until it stops. Graeme Gill.