Re: Skirmish with .NET Framework versions 2.0, 3.0, 3.5 following update to SP1

On Thu, 18 Jun 2009 19:00:36 +0100, "Doug"
<> wrote:


> Off topic, when I took my box in to the manufacturer to have an extra 2GB
> fitted to make 4GB, I was surprised when I got it home to find the
> technician had removed the swap file. After trying it with a fixed swap file
> of around 9GB and reading up about it, I decided that opinion was evenly
> divided and that he was probably right.



He was not right.


> The space is welcome, the disc
> thrashing reduced, everything seems faster, and PerfectDisk has less
> defragging to do.


There's no reason to have a fixed size. There's no advantage to not
having a page file, and often a disadvantage.

1. If you don't have a page file, you can't use all the RAM you have.
That's because Windows preallocates virtual memory in anticipation of
a possible need for it, even though that allocated virtual memory may
never be used. Without a page file, that allocation has to be made in
real memory, thus tying up that memory and preventing it from being
used for any purpose.

2. There is never a benefit in not having a page file. If it isn't
needed, it won't be used. Don't confuse allocated memory with used
memory.

--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup

"Ken Blake, MVP" <> wrote in message
news:...
> On Thu, 18 Jun 2009 19:00:36 +0100, "Doug"
> <> wrote:
>
>> Off topic, when I took my box in to the manufacturer to have an extra 2GB
>> fitted to make 4GB, I was surprised when I got it home to find the
>> technician had removed the swap file. After trying it with a fixed swap
>> file
>> of around 9GB and reading up about it, I decided that opinion was evenly
>> divided and that he was probably right.
>
> He was not right.
>
>> The space is welcome, the disc
>> thrashing reduced, everything seems faster, and PerfectDisk has less
>> defragging to do.
>
> There's no reason to have a fixed size. There's no advantage to not
> having a page file, and often a disadvantage.
>
> 1. If you don't have a page file, you can't use all the RAM you have.
> That's because Windows preallocates virtual memory in anticipation of
> a possible need for it, even though that allocated virtual memory may
> never be used. Without a page file, that allocation has to be made in
> real memory, thus tying up that memory and preventing it from being
> used for any purpose.
>
> 2. There is never a benefit in not having a page file. If it isn't
> needed, it won't be used. Don't confuse allocated memory with used
> memory.
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup

Thanks, Ken, I shall certainly give this further attention.
Doug


__________ Information from ESET Smart Security, version of virus signature database 4169 (20090619) __________

The message was checked by ESET Smart Security.

http://www.eset.com

On Fri, 19 Jun 2009 07:19:19 +0100, "Doug"
<> wrote:

> "Ken Blake, MVP" <> wrote in message
> news:...
> > On Thu, 18 Jun 2009 19:00:36 +0100, "Doug"
> > <> wrote:
> >
> >> Off topic, when I took my box in to the manufacturer to have an extra 2GB
> >> fitted to make 4GB, I was surprised when I got it home to find the
> >> technician had removed the swap file. After trying it with a fixed swap
> >> file
> >> of around 9GB and reading up about it, I decided that opinion was evenly
> >> divided and that he was probably right.
> >
> > He was not right.
> >
> >> The space is welcome, the disc
> >> thrashing reduced, everything seems faster, and PerfectDisk has less
> >> defragging to do.
> >
> > There's no reason to have a fixed size. There's no advantage to not
> > having a page file, and often a disadvantage.
> >
> > 1. If you don't have a page file, you can't use all the RAM you have.
> > That's because Windows preallocates virtual memory in anticipation of
> > a possible need for it, even though that allocated virtual memory may
> > never be used. Without a page file, that allocation has to be made in
> > real memory, thus tying up that memory and preventing it from being
> > used for any purpose.
> >
> > 2. There is never a benefit in not having a page file. If it isn't
> > needed, it won't be used. Don't confuse allocated memory with used
> > memory.
> > --
> > Ken Blake, Microsoft MVP - Windows Desktop Experience
> > Please Reply to the Newsgroup
>
> Thanks, Ken, I shall certainly give this further attention.


You're welcome. Glad to help.

--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup