Disable virtual memory(pagefile)NOT!

Redneck

No gain in doing so
Nothing will be faster
Windows is supposed to use it in the first place
Having 2Gig or more of ram will not make any difference to it

C.Joseph S. Drayton

Redneck wrote:

>No gain in doing so
>Nothing will be faster
>Windows is supposed to use it in the first place
>Having 2Gig or more of ram will not make any difference to it

Hello Redneck,

I would have to disagree with you. I have read a number of papers on
the subject, and about 75% of them agree with you. I tend to deal in
real world usage where design theory sometimes runs into snags . . .

On my computer running WindowsXPpe[sp2], for most processes except for
large file management (ie. copying files totalling more than 5GB), I
tend to get better performance with the pagefile turned off.

Most of my programming is in Clarion5.5ee[h] and the increase in
compile speed is 30% - 55% (the major factor seems to be the number of
3rd party templates I am using). Clarion also does not like
hyperthreading or dual core CPUs, it ties itself to a single thread or
core (no I don't know why SoftVelocity has done this).

It is all well and good to state these general 'rules', but there are
times when applications break those rules. More often than not I see
'rules' like this stated here so that the user who doesn't want to take
the time to learn about their machine and wants their hands held can be
'protected' which is fine . . . just don't imply that the rule is
engraved in stone. I've been playing with computers for 30+ years, and
hardware and software makers are both constantly pushing the envelope
so rules of this type tend to be more recommendations than actual rules.

As an aside, the only time I turn on my pagefile is when I am running
Photoshop Design Studio CS3 and that is because I haven't found a way
to make it run without checking for a pagefile.

--

Sincerely,
C.Joseph Drayton, Ph.D. AS&T

CSD Computer Services

Please excuse the TEMPORARY web site

Web site:
E-mail: