Which parts are the worst resource hogs?

[wildeh]

Hi, is there a document explaining the effect of certain setting on the performance? I.e. which parts should be removed and which parts don't make a big difference installed or not.

Thanks!

[Guest]

No such document exists. I would say unless you strip the thing bare you're not going to notice much. I used to strip Win2k/XP but I no longer remove components. It's a hassle seeing if a Windows update is for something that has been removed. Plus my event viewer is no longer full of errors.

[Martin H]

The biggest hogs are services and other components with dlls in memory at run-time...

Anyway, here's a quote from nuhi about this:

you won't believe this but most of the people believes that that it cannot possibly help, that all we do is break our OS. Well I'm patient and I don't care any more of those "blasphemers" but it sure is nice to read this topic in the times of such fast hardware.

I'm having the same experience and so does anyone who used nLite to it's fullest. Of course it can go the wrong way (frustration) if you're not into it and not ready to do some trials, then stick to the full version.

Biggest improvements are because of the removed services/components, not just disabled, because nLite removes those files before install so they are not registered nor in the memory (emphasis on the threads and handles, not actual memory size), while that disable option (post install, services) is kinda questionable (definitelly not clearing the reg). To remind of add/remove programs for IE and WMP (just removes the icon and hides the files).

Emphasis is mine.

Source: http://www.msfn.org/board/index.php?s=&amp...st&p=626226

I can't say for the newest boxes(as i don't own one), but on the mid-range/old systems, i would say that there defenetelly is something to archive with reducing the OS performance-wise...

As for updates, i have always just found it to be easier and much less of a hassle to just download and archive/use all the Windows core updates... However, i don't have that issue anymore, as i now prefer to just use an update-pack instead(since nLite uses the QFE branch for direct integration, whereas i want the GDR branch, and also nLite can't directly integrate all the updates and for those it can't, then it instead uses the updates own bloated '/integrate' switch method)...

Edited August 19, 2009 by Martin H