![]() |
Try and experiement with different maxmem settings too 512, 600,640, 670... also play with the waza file size in spi tweaker. 1024k and 512k are my favs. And remember higher available memory doesnt necessarily mean better waza, but it can indicate that (verify with final scores). Sometimes the "CDT" or "IV" options have helped my times so try those too. Most of pi tweaking is system subjective so you will have to experiment with values, until you find what your OS/bios/etc likes. Just my $.02
|
Thanks karmakazi! When this comp is over I plan on playing lots of 32m. I really wanna learn the ins and outs of this bench.
|
Quote:
From TechNet: Windows allocates a portion of the virtual memory in your system to the file system cache. The file system cache is a subset of the memory system that retains recently used information for quick access. The size of the cache depends on the amount of physical memory installed and the memory required for applications. The operating system dynamically adjusts the size of the cache as needed, sharing memory optimally between process working sets and the system cache.And why Wazza is effective: Frequent cache flushing might occur if data is written to the disk frequently in order to free pagesIf your running on XP/2003, open Task Manager and you can watch it grow during CW file copy. |
Quote:
|
Good Read
Quote:
Interesting read.... |
Quote:
|
I've only used spitweaker for waza, but only for a couple runs. I have taken about 30 seconds off by finding the right pagefile for that particualar install. Now I just need to find my "range" to test with each install to find the best quickly.
|
Quote:
|
I will have to dig it up. I am on my phone right now. I had to dig a little to find a good d/l of version 1.6.
|
Quote:
|
| All times are GMT -10. The time now is 01:52 PM. |
Copyright ©2009 Overclockaholics.com