Agreed, EXCELLENT work. In fact I joined anandtech just to say so!
I'll bet a lot of sites end up linking to this thread.
deathkoba> However, it DOES reduce the amount of memory the system uses
Well, not necessarily even that. The memory "used by services" (and the file cache, and every other process or set of processes) is a highly dynamic quantity. If nothing else is placing demands on RAM, the services will pretty much be left as they are after startup (and even these sizes depend greatly on how much RAM is on the machine).
But that isn't a typical situation, and if it is your situation, who cares? You don't need the RAM for anything else in that case.
otoh if you do run some apps that make more demands on RAM than can be immediately satisfied, the idle services procs will have their working sets ("mem usage" in task manager) shrunk (just as with any other process).
Unless of course the service process is busy too... but if it's busy, it's presumably doing something for you, so you don't want to disable it anyway.
Disabling services to save memory does make the memory available earlier, without waiting for the OS to shrink any working sets... but that's a tiny benefit. If you see it at all you'd see it in app startup times, not in "operational" performance of the apps.
I'll bet a lot of sites end up linking to this thread.
deathkoba> However, it DOES reduce the amount of memory the system uses
Well, not necessarily even that. The memory "used by services" (and the file cache, and every other process or set of processes) is a highly dynamic quantity. If nothing else is placing demands on RAM, the services will pretty much be left as they are after startup (and even these sizes depend greatly on how much RAM is on the machine).
But that isn't a typical situation, and if it is your situation, who cares? You don't need the RAM for anything else in that case.
otoh if you do run some apps that make more demands on RAM than can be immediately satisfied, the idle services procs will have their working sets ("mem usage" in task manager) shrunk (just as with any other process).
Unless of course the service process is busy too... but if it's busy, it's presumably doing something for you, so you don't want to disable it anyway.
Disabling services to save memory does make the memory available earlier, without waiting for the OS to shrink any working sets... but that's a tiny benefit. If you see it at all you'd see it in app startup times, not in "operational" performance of the apps.