Humm, that article isn't entirely correct.
For instance...
Disable the PagefileThey claim that there's no performance benefit from disabling the paging file... well, that's not true. Windows tends to page out to disk in a lot of situations where it doesn't really make sense (partially because of badly designed usermode programs, though). So if you have plenty (at least a gig, 2gig preferred) you can avoid some needless paging by turning off the paging file. It's not a big improvement for most situations, but it does help a little.
Of course if you run anything from Adobe, forget about turning off your paging file... Adobe apps are badly designed monsters that don't have decent memory management. And of course, some games have extreme memory requirements as well (funny enough a relatively simple game like PainKiller uses enough memory that a gig of ram + no paging file crashes on some levels).
Also note that this only works for XP, Windows 2000 and below require at least a minimal (~20meg) paging file, and will create one at boottime if you've disabled it.
The article also seems to confuse 80386 protected mode "virtual memory"/"paging" with the process of paging in/out from disk - just because 80386 paging is enabled doesn't mean you have to page (or swap) to disk.
Large System Cache TweakThis tweak can be nice on Desktop machines, not just servers, depending on the way you use your system. For me this is a VERY nice tweak. It means that, for instance, when I've used nLite to create a slipstreamed install CD, once the files are prepared and I go to the ISO creation stage, almost all files will be in the filesystem cache, so almost all reads will go from memory instead of drive... lots faster.
but the changed pages occupy memory that might otherwise be used by applications is a moot point, since filesystem cache will always be dropped when applications request memory and there's currently not enough free memory.
On workstations this increases paging and causes longer delays whenever you start a new app. is plainly wrong, there's actually a better chance of your .exe and .dlls being in memory (equals shorter loading time) if you have LargeSystemCache=1.
HOWEVER, never use LargeSystemCache=1 on machines with ATI graphics cards and drivers. ATI drivers are nasty... see
this post.