[Mogens V.]

Laurence Payne wrote:
On Mon, 22 Oct 2007 09:50:42 -0400, "Sean Conolly"
wrote:


But why on Earth WOULD it be "swapping heavily" (whatever that means?)
Sure, you can sabotage any recording by running another disk-intensive
process behind it. Which is why you don't :-)

Page swaps is one good source of background writes, and you can have a lot
of swap activity well before you out of physical memory (at least on
windows, don't know about mac).


As (again) I've had to say too many times: on a PC with adequate RAM
(and there's no excuse these days for a DAW not to have this)

Sure, ram is cheap, but not all (non-new) mobos are designed to easily
take more than 4GB ram. Of cause, just swap the mobo and cpu and ram..

go into System and completely disable the on-disk paging file. Don't argue it
can't be done, or get tied up in the two usages of the term "virtual
memory". Just do it. Then reboot, and watch your computer perform
precisely as before.

Until ressources are exausted. Pls, don't repeat the 'no excuse for
ram', because someone may actually stack enough synth et al or whatever
to exaust a 4GB system. Yes I deliberately skipped systems with 8-20+GB
ram, to illustrate that your advice is ill adapted for non-experts.

You're absolutely correct that it's fully possible to run without a
pagefile, but this should only be done fully knowing every operating
situation with every intended use, which you don't mention here.

A more useful approach is setting the pagefile to a large _fixed_ size,
so Windblows doesn't spend energy on re-sizing it as it thinks needed,
then use some utility to ensure it's one contigious file and move it to
front of disk.

(A few programs do like to see a paging file on disk, though I don't think

IOW, you don't know.. Which programs, BTW? Do userspace programs
directly use the pagefile? Or do they aquire ressources from the _OS_,
which then use the pagefile as needed (or dreamt up by programmers) ?

Programs don't ask for diskspace to live on; all they can do is use some
version of malloc() to get more memory, which to them is just.. memory..
It's the OS that arbitrates between ram and disk.

they use it for what you think they do. So,
having proved the point, reset it.)


--
Kind regards,
Mogens V.