Why would the RAM size be considered as a factor, it's a security feature? Obviously the more concurrent users you got, the more RAM will be consumed by duplicated services.
But you're not running a Terminal Services server for 15 remote users logged in at once. Someone is, but not you.
The challenge of adding a new NTLite UI to manage per-user Services is AFAIK they're not specially marked as such by Windows. There's a published list of known services, but it might change over time. Granted, it hardly every changes these days.
A kludgy fix is running a script to cycle through a list of all know Services, and appending UserServiceFlags to their keys even if they don't care about it. It's one of those problems where not enough users would be asking for it, unless nuhi's super bored.
according to winaero and w10forum the tweak to reduce instances of svchost varies on the ram. the reg file way is much better if you are building a one size fits all image. i would check your reg against the target image incase it differs, prolly not but worth a look.
These are slightly different conversations--Clang2 is inquiring if the "Per-User Service" tweak is related or works alongside the "SvcHostSplitThresholdInKB" tweak that has been discussed a few times on the forum (link1, link2). I think the answer is it's similar in concept, but not directly related, and I explain it in a way that all skill levels can follow below, because I think they're both cool tweaks to experiment with, and I want to make this information more digestible for the masses.
PER-USER SERVICE TWEAK
I haven't seen the Per-User Service tweak until today (I'm certainly intrigued to experiment with it!), but what I'm understanding is that if you go to Start > Windows Administrative Tools > Services and look at the Name column there are some that have a suffix with random numbers that change every reboot, such as AarSvc_2cb0d, which is the first in my list.
If I reboot, the 2cb0d will change again, because the Per-User Service tweak being enabled tells some services to provide an extra layer of security by duplicating themselves for each user on the machine. In other words, hidden behind the scenes is another AarSvc service running too, but that one might be AarSvc_2xd3f, because it belongs to my wife's account that she was logged into earlier in the day.
The Per-User Service tweak allows us to manually disable the duplication (suffixes) in each of the services that duplicate themselves. Disabling the duplication will decrease security, but reduces overall resource usage.
SERVICE HOST SPLIT THRESHOLD TWEAK
For the SvcHostSplitThresholdInKB tweak, go to the desktop and press ctrl+alt+del to bring up Task Manager and select "Processes" on the top left. Next, click on the "View" button at the top and ensure "Expand all" is checked. Scroll down until you start seeing many instances that start with the name, "Service Host:" and note how some contain 1 item inside, while other containers have several.
Microsoft made it so that idle memory usage is increased in machines that have more total RAM installed, and decreases in machines that have less total RAM installed, in order to allow the Service Host containers to add or substract additional items inside them.
The benefit is that fewer items inside each Service Host improves the stability (crashing) of the machine at the cost of increased idle memory usage, because the downside to having multiple items inside a single container is that if one item crashes, it might cause all the others in the group to malfunction as well, which means greater system-wide instability from the cascading effect.
It should be pointed out every time it's mentioned, that the SvcHostSplitThresholdInKB is the single biggest reason why so many "gamer" operating systems appear to be awesome on the surface, because this tweak can tremendously lower the resource usage of Processes, Threads, Handles, and Memory when adjusting it towards instability. It's also the reason why Virtual Machine (VM) installs have artificially lower Task Manager screenshots, because Windows is adjusting itself automatically based on the allocated memory.
The svchost thing is a parent process split, where all the actual Services are now executed by forking off distinct svchost threads, and each thread owns one Service process. Part of this is a big accounting trick, like how modern browsers keep forking copies to host new tab instances.
Splitting the threads offers improved reliability and security, since a crashed Service doesn't cause upstream problems since they're not sharing a smaller pool of svchost processes. Unless you have a low memory PC (like below 8 GB RAM), it's not a huge factor.
When the average new PC has 16 GB (as per current MS standards), this ain't a big deal today.
These are slightly different conversations--Clang2 is inquiring if the "Per-User Service" tweak is related or works alongside the "SvcHostSplitThresholdInKB" tweak
Suggestion on pricing... bit weird to do BF (November) and Xmas (December) discounts only... I'm just gonna have to wait till November to register... if you ditched the Xmas one and had a June or July one you'd spread your income over the year rather than lump it into November and December...
Or you can send me a special discount to buy now - I'm easy
Suggestion on pricing... bit weird to do BF (November) and Xmas (December) discounts only... I'm just gonna have to wait till November to register... if you ditched the Xmas one and had a June or July one you'd spread your income over the year rather than lump it into November and December...
Or you can send me a special discount to buy now - I'm easy
Discount pricing is typically reserved for Black Friday and New Year's. Unactivated licenses don't expire, so you can purchase a new one (or renewal) ahead of time and activate it later.
Following current trends, a new Windows release usually ships around late September or early October in order to match the Holiday buying season for new PC models. It's also typical to wait until a month or two after RTM, when most of the early Windows bugs get fixed.
For a casual user that only switches Windows once a year, the discount timing works out for them.
nope. if someone asks in forum if anyone has sample-versionX.exe and they cant find it(or find it from a trusted source) then i will one drive or mediafire it. or if they need a file hash comparison i can check against my copy.
These are slightly different conversations--Clang2 is inquiring if the "Per-User Service" tweak is related or works alongside the "SvcHostSplitThresholdInKB" tweak that has been discussed a few times on the forum (link1, link2). I think the answer is it's similar in concept, but not directly related, and I explain it in a way that all skill levels can follow below, because I think they're both cool tweaks to experiment with, and I want to make this information more digestible for the masses.
PER-USER SERVICE TWEAK
I haven't seen the Per-User Service tweak until today (I'm certainly intrigued to experiment with it!), but what I'm understanding is that if you go to Start > Windows Administrative Tools > Services and look at the Name column there are some that have a suffix with random numbers that change every reboot, such as AarSvc_2cb0d, which is the first in my list.
If I reboot, the 2cb0d will change again, because the Per-User Service tweak being enabled tells some services to provide an extra layer of security by duplicating themselves for each user on the machine. In other words, hidden behind the scenes is another AarSvc service running too, but that one might be AarSvc_2xd3f, because it belongs to my wife's account that she was logged into earlier in the day.
The Per-User Service tweak allows us to manually disable the duplication (suffixes) in each of the services that duplicate themselves. Disabling the duplication will decrease security, but reduces overall resource usage.
SERVICE HOST SPLIT THRESHOLD TWEAK
For the SvcHostSplitThresholdInKB tweak, go to the desktop and press ctrl+alt+del to bring up Task Manager and select "Processes" on the top left. Next, click on the "View" button at the top and ensure "Expand all" is checked. Scroll down until you start seeing many instances that start with the name, "Service Host:" and note how some contain 1 item inside, while other containers have several.
Microsoft made it so that idle memory usage is increased in machines that have more total RAM installed, and decreases in machines that have less total RAM installed, in order to allow the Service Host containers to add or substract additional items inside them.
The benefit is that fewer items inside each Service Host improves the stability (crashing) of the machine at the cost of increased idle memory usage, because the downside to having multiple items inside a single container is that if one item crashes, it might cause all the others in the group to malfunction as well, which means greater system-wide instability from the cascading effect.
It should be pointed out every time it's mentioned, that the SvcHostSplitThresholdInKB is the single biggest reason why so many "gamer" operating systems appear to be awesome on the surface, because this tweak can tremendously lower the resource usage of Processes, Threads, Handles, and Memory when adjusting it towards instability. It's also the reason why Virtual Machine (VM) installs have artificially lower Task Manager screenshots, because Windows is adjusting itself automatically based on the allocated memory.
think you got that back to front. it reduces instances but probably keeps the same(maybe a bit less) ram use because of the processes so where you had 20 processes using 20 instances you now got 20 processes now using only 10(as an example) instances. to be honest i never checked the difference in ram use, i just look at handles threads and processes count.
think you got that back to front. it reduces instances but probably keeps the same(maybe a bit less) ram use because of the processes so where you had 20 processes using 20 instances you now got 20 processes now using only 10(as an example) instances. to be honest i never checked the difference in ram use, i just look at handles threads and processes count.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
