[Thermodyne]

Originally posted by JoeViterbo:
The configuration of virtual memory even depends on your Version of windows. i think windows xp can even manage multiple page-files.

On rule to speed up things is: if you have two drives, put them on different controllers. Put your resource-consuming application to the drive where the page file is NOT. So using the page file and reloading software components won't interfere.

It is not a good solution to turn of the virtual memory. If you run multiple applications, your system will soon need it. Btw: Windows usually writes first the data to disk, that appears to be less important( e.g. idle apps etc )

quote:

---

All things ram are done in 32’s, 32-64-128-256-512-1024. Try to work the page file size in the same increments. It eases the addressing load on the CPU.

I think the cpu runs in protected mode anyways. So every address is 32-Bit. There are no more "far" and "short" jumps. the cpu accesses each (even)adress at the same speed.

---

XP and 2K can both manage more than one page file.

The reason for x32 page file size goes back to the original x86 code, and the function of the data buss. Take a look a the default page file size that windows sets. It will vary with the amount of ram installed, but it will always devide by 32.

A bench mark trick is to run a small page file. Just enough to meet the needs of the mark being run. Some times it will be 1meg or even 1/2 a meg. If you vary from x32, you will see it in the results.