LargeSystemCache

There's a memory management reg key for LargeSystemCache that allows the OS to cache larger files. I think it's recommended for servers - what about for an OS?

Another Server performance tweak is the CriticalWorkerThreads and the Delay. I'm also curious if anyone's tried this. MS suggests changing the value for "10" for servers but to make sure you find the "sweet spot." Anyone test their machines to find that spot?

If you're feeling adventurous and helpful try some before/ after benchmarks with the threads.

 

To me it seems like the cache are allowed to get as large as the RAM size - 4 MB, and may severely affect graphics performance.
Neither sounds good to me.
It may be outdated info from XP tho.

If you want to improve speed, try a RAMdisk instead.

 

From what I saw it just changes the size of the files that can be cached so now if you use a 1GB file frequently that file will be cached.

I'd be interested in hearing more, especially about the threads.

 

It is a registry tweak which allows the filesystem to occupy more pages in memory for file operations in the storage subsystem. It is useful for servers running a file server, but not useful for workstation performance because applications are dynamically using pages in and out like crazy. Enabling a larger system cache will actually reduce graphics performance of machines that use shared memory from the system because less memory is able to be pulled into the system and used as VRAM.

 

Interesting, thank you.

And what about the WorkerThreads tweak?

 

I have implemented the critical worker threads and Win32PrioritySeparation tweaks on my server for improved application responsiveness. Given that I am using Windows Server as a hybrid workstation/server I reek the benefits due to my substantial system RAM available (8GB). More RAM is required for running each application in its own memory window but the benefits are noticeable. My applications load wicked fast on this OS.

If you have atleast 4 GB of RAM,

Set "additionalcriticalworkerthreads" to decimal value of 8
Set Win32PrioritySeparation to decimal value of 22.

EDIT: Correction I meant 22 I was typing too fast and I accidently put default value out of instinct.

Application responsiveness on startup should be much improved.

As a side note, I previously recorded my Passmark results of my machine before the above mentioned registry tweaks.

My results before:

CPU Mark: 3339.2
Memory Mark: 1288.4
Total Passmark Score: 1280

My results after:


CPU Mark: 3362.2 (+1%)
Memory Mark: 1361.5 (+5%)
Total Passmark Score: 1303 (+2%)

Not too shabby.

 

What does win32PrioritySeparation do?

EDIT: Just testing a bit but I can set the worker threads to any value it seems. Checking the additional threads in task manager shows that there's a change. I went as high as 40 but took it back down.

Too lazy to run benchmarks though I'd love for someone else to.

 

The maximum number of threads is 16.

As far as the win32PrioritySeparation, you have probably seen it from the GUI countless times. It is located in Advanced System Settings > Advanced > Performance > Settings... > Advanced. You will see two options:

Adjust for best performance of:

( ) Programs ( ) Background services


A hex value of 0x0000026 (38) is the default value for "Programs"

It gives 18 quanta for foreground applications, 6 for background.

A hex value of 0x0000018 (24) is the default value for "Background services"

Changing the hex value to 0x00000016 (22) will give you 6X more CPU time dedicated to foreground applications which is very useful for workstation purposes.

 

I see - thank you. I'll leave that as default.