vaibhav011286
Member
- Downloaded
- 18.8 GB
- Uploaded
- 24.1 GB
- Ratio
- 1.28
- Seedbonus
- 3,615
- Upload Count
- 0 (0)
Member for 6 years
wow!!! such an awesome work... keep it up bro.. thanks a lot
try Microsoft Keyboard Layout Creator and add the language you like.This is such a dream, I love it. Sadly, without different keyboard layouts it's unusable for me :/
I love reading what you write, you were talking about core number and which version, LTSB/C. i have 16 cores/16 threads x2. 6386SE Opterons OCd to 4 GHz. What LTS bui;d would you recommend for me? No gaming, just Music and rendering images and stuff. I know this is the wrong place to ask. sorryIt's a fairly technical subject, maybe deserving its own thread and not hijacking this one but long story short.
Let's say you have 1 worker, and there are 10 tasks that each take an hour to finish.
If he does one task, he will be 1 hour. If he does 2 tasks concurrently he will need 2 hours and 5 minutes. Why the 5? he needs t check where each task is currently and so he can pick where he left off, we call it overhead. If he does 3 tasks it will take 3 hours and 10 min and so on... Windows do the same more or less but only with active tasks. By default, LTSB has fewer active tasks than other versions, even after removal, and the version of those services are much simpler due to the release date. Compare for example the defender of LTSB and defender of 21h1. You will see that LTSB does far fewer things which also make defender a more light (but less secure) antivirus. At the same time that makes the CPU usage of the 2 defenders unequal as the LTSb defender does fewer things and has less impact than the 20h1. Again this is just an example as I am aware that probably both optimized version would have it off but I just wanted to make a point. The same applies to other things too like, fewer internal metrics for user experience since LTSB never had the store, edge, etc. No need for update services since it only gets security and not core updates... the list is long, but essentially this concept is what gives LTSB the performance advantage in most cases.
What I was trying to tell you is that even tho defender, update, index, etc do run as services and shutting down said services it means CPU has fewer tasks to bother with, not all services bother the CPU. For example, print spooler since is popular these days have zero effect on CPU and minimal on ram (5k) unless it's used, and even then, it's ONLY as long as it's been used (when printing or making PDF for example) and on a 4 core CPU is less than 0,1%. Not all services are equal when it comes to CPU utilization. So closing selectively some services does benefit performance, and even better not having them at all, to begin with (LTSB/LTSC) but that doesn't mean that all services cause delays or drop performance. Some actually increase it. It's not therefore the No of services that matter, but knowing which services to switch off or not.
At another point, we may dig deeper into the technical side of things, probably when the new LTSC comes out (now in early alpha).
Hope it helped.