[OT] virtual memory

[Ruatha]

Ok Thermo I see your point but it's still misguided.
If you change your page file to 32 M it doesn't matter if it 's anywhere between 16M+1 byte and 32M, it still has the same adress range, so having 32M doesn't make it go any faster than having 30M!
It's not some magic number, it's simply logic.
If you change from 32M to 32M+1 byte it can have some insignificant affact, hardly noticable I'd think but I'd agree that you might see it with a benchmark, haven't tested though, bit from say 24M to 29M or 32M it wouldn't have any aeffect, i e 32M page file is not faster then 24M pagefile.

The reason windows et it to "size dividable with 32" is that it want's the maximum amount possible if it's going above "size divided by 32" +1 byte, but youas a thinking human might hav ereasons not to set it that way.
And I've seen "not even dividable by 32" sizes if the free part of the disk doesn't allow it.
See?

[ August 02, 2003, 08:45: Message edited by: Ruatha ]

[Thermodyne]

Not exactly, but also true. As systems have gotten faster, page file virtual addressing has gotten more transparent, the load is a very small percentage of CPU time now. But the system still expects to see a size based on Base2 binary, starting with a 1 and then being all zeros. It will write each page as a 4kb page or slice of data. A simple way of seeing this is to enter 1 and a 0 into your electric slide rule, then look at the result. Repeat the process adding a zero each time. The results will be well known numbers.

Here is a link to the best place I know to get plain English answers on this stuff.

http://aumha.org/win5/a/xpvm.php

If you need more details, then we suffer the Chinese horror of the 1000 white papers 

[Ruatha]

That was a good link!

[Thermodyne]

Glad you liked it

In the long gone days of win98, this guy was the keeper of the grail for those of us who couldn’t deal with the white papers.