Make the process count in Performance smaller

[tonho888]

morning nihu….
how do you make the process in performance small like that, what should I do? when I make an iso it's never small like this the process is in terms of performance, the smallest is around 85-100, on a real machine/vhd format the process is always big but small when running on vboxView attachment 9929

 

[garlin]

nuhi doesn't provide any performance tuning or debloating advice, other than sharing NTLite's templates.

There are many forum guides, and recent posts about reducing idle CPU utilization and thread count. Look around.

VM's are useful for testing software, but terrible for modeling real-world performance. Your VirtualBox is emulating a CPU with limited number of cores and not enough physical memory (2 GB). When you increase the CPU cores and RAM, or move to a physical machine, the numbers will change as the system will have more resources available.

 

[nuhi]

Try Components - toolbar - Templates - Lite, and as garlin stated test in a virtual machine until you hit the goal.

You can also jumpstart it even more precisely by:
Load source image.
Go to Components - Compatibilities - disable those not needed - OK
Go to Images - Preset - Save - Extract current image state - OK
Image - New session
Load destination image
Load the saved preset and apply changes

 

[Hellbovine]

That screenshot is mostly due to the registry tweak called, SvcHostSplitThresholdInKB (link).

Txmmy adds it into his GamerOS scripts (the new and old one), so some people here use the tweak, but nobody here has posted results on if it's a good or bad tweak, since it's not super common yet. I suspect it will have an affect on DPC latency, and by using the tweak it may actually decrease performance, but this is theory for now until I have time to thoroughly investigate it. My only point here is be careful about using the tweak because if you aren't going to test it properly, then it may make some circumstances worse, such as gaming.

So what is the tweak in simple terms? Well, if you open task manager and look at all those svchost processes running, you can click "expand" on them and see what features they contain inside. In older Windows, many features were grouped inside svchost processes, and by doing that it greatly reduced the system resource usage. The negative though, is a computer could be more prone to crashing if one of those processes misbehave because if there is a group of 10 processes inside an svchost container and just 1 of those bugs out, it can cause the other 9 to crash too. Microsoft had purposely pulled them out of containers in order to improve overall stability, but that came at greatly increased resource usage.

This tweak is why you have to be really careful about the hype surrounding custom gaming ISO (link) because it's stupidly easy to get low task manager resource usage without doing any real tweaking, by using this. In other words, it's easy to deceive people about how good the performance of a custom image is since the numbers can be manipulated effortlessly.

 

[Clanger]

because it's stupidly easy to get low task manager resource usage without doing any real tweaking

This took pigheadiness time and wherewithal(best of all, there wasnt a single removal apart from Defender). Havnt been impressed with any of those "lite" iso's yet and i doubt i ever will be, unless i build it myself.

 

[Clanger]

suspect it will have an affect on DPC latency,

More people should try tweaking the kernel timer latency, default on mine is around 1000μs, tweaked im looking at 10 to 20μs.

 

[Clanger]

The reduce svc host tweak does work well but as hellmoo says if one instance of svchost crashes it wipes out other things aswell as the culprit process but i dont remember any crashing when using that tweak. Winaero Tweaker has that tweak so try it through that because its easily reversed if all hell breaks loose.

 

[Hellbovine]

Just to add-on a bit for potential followup questions, attached is a screenshot from a very stable custom image (W10 21H2) that has been extensively tested, and this is what most people can expect to achieve with enough time and effort (or by using a preset or guide) on W10/W11. For people that don't want to login to view the screenshot, the processes are at 89, threads at 646, handles at 27423, with 1.0 GB memory used, and no CPU or disk activity. This is before drivers and other software gets installed though, so the numbers will quickly rise again if you install too much bloat.

Numbers lower than this are almost always manipulated in some way, riddled with bad tweaks, or are using the previously discussed registry key. You can still lower the resources much further, but you start to get into trade-off territory where you may lose functionality in order to gain resources with additional tweaking from this point forward.

That last paragraph is a generalization though because I could also easily make an image where I got to these same task manager results as the screenshot I posted, but broke 100's of dependencies along the way, resulting in a buggy image. It really depends on the tweaking approach, and I'm not going to elaborate further because it gets to be too much, and in order to better understand all of this people need to just experiment with NTLite and general tweaking to gain the necessary knowledge and experience (or skip all that work and use someone's preset/guide and call it a day).

 

[tonho888]

Just to add-on a bit for potential followup questions, attached is a screenshot from a very stable custom image (W10 21H2) that has been extensively tested, and this is what most people can expect to achieve with enough time and effort (or by using a preset or guide) on W10/W11. For people that don't want to login to view the screenshot, the processes are at 89, threads at 646, handles at 27423, with 1.0 GB memory used, and no CPU or disk activity. This is before drivers and other software gets installed though, so the numbers will quickly rise again if you install too much bloat.

Numbers lower than this are almost always manipulated in some way, riddled with bad tweaks, or are using the previously discussed registry key. You can still lower the resources much further, but you start to get into trade-off territory where you may lose functionality in order to gain resources with additional tweaking from this point forward.

That last paragraph is a generalization though because I could also easily make an image where I got to these same task manager results as the screenshot I posted, but broke 100's of dependencies along the way, resulting in a buggy image. It really depends on the tweaking approach, and I'm not going to elaborate further because it gets to be too much, and in order to better understand all of this people need to just experiment with NTLite and general tweaking to gain the necessary knowledge and experience (or skip all that work and use someone's preset/guide and call it a day).

I just wanted to comment as above but not from the treat you gave but from the MT_ treat, in the MT-LTSC1809 low level tweak.reg tweak folder, and I tried one of these, but it's easy if it's wrong, just restart and close the super client. I tried this on diskless, so when someone enters the wrong reg, just restart it. So you think the process I'm working on is correct, even though the results are big like your photo above, sorry if my language is confusing, but I thank you, this is where I learned and find it very helpful

 

[Clanger]

processes are at 89, threads at 646, handles at 27423

No way in heaven or hell will i accept those numbers for a non bareboned services machine, handles between 12000 and 15000 yes. I can get 6xxx handles(less if i remember correctly) for an online w7 machine so double that at most because 10 is a resource eater just as 7 was a resource eater compared to xp.

 

[tonho888]

Try Components - toolbar - Templates - Lite, and as garlin stated test in a virtual machine until you hit the goal.

You can also jumpstart it even more precisely by:
Load source image.
Go to Components - Compatibilities - disable those not needed - OK
Go to Images - Preset - Save - Extract current image state - OK
Image - New session
Load destination image
Load the saved preset and apply changes

didn't change anything sir, because when I saved the preset from the beginning the component was not checked, and I edited it manually to "no" everything

 

[tonho888]

No way in heaven or hell will i accept those numbers for a non bareboned services machine, handles between 12000 and 15000 yes. I can get 6xxx handles(less if i remember correctly) for an online w7 machine so double that at most because 10 is a resource eater just as 7 was a resource eater compared to xp.

sir please don't read my mind right now, coz what u said I really want to achieve, are you a psychic?

 

[Clanger]

Time effort and determination will get you what you want. I could quite easily get away with using XP, i dont need all this modern junk.

 

[tonho888]

Time effort and determination will get you what you want. I could quite easily get away with using XP, i dont need all this modern junk.

yes, that's right, I tried it more than 30 times, restart shutdown and no ntlite, special "preset" I'm blind, thanks everyone

 

[Kennkish]

Just to add-on a bit for potential followup questions, attached is a screenshot from a very stable custom image (W10 21H2) that has been extensively tested, and this is what most people can expect to achieve with enough time and effort (or by using a preset or guide) on W10/W11. For people that don't want to login to view the screenshot, the processes are at 89, threads at 646, handles at 27423, with 1.0 GB memory used, and no CPU or disk activity. This is before drivers and other software gets installed though, so the numbers will quickly rise again if you install too much bloat.

Numbers lower than this are almost always manipulated in some way, riddled with bad tweaks, or are using the previously discussed registry key. You can still lower the resources much further, but you start to get into trade-off territory where you may lose functionality in order to gain resources with additional tweaking from this point forward.

That last paragraph is a generalization though because I could also easily make an image where I got to these same task manager results as the screenshot I posted, but broke 100's of dependencies along the way, resulting in a buggy image. It really depends on the tweaking approach, and I'm not going to elaborate further because it gets to be too much, and in order to better understand all of this people need to just experiment with NTLite and general tweaking to gain the necessary knowledge and experience (or skip all that work and use someone's preset/guide and call it a day).

Is the xbox sh*t turnt off? if not then you have some more to go down ))