To put it simply different instructions use different parts of the CPU and instructions used for waiting for input don't heat up the CPU much.Īs for lack of optimization, well that's a really big topic which mainly depends of what you consider as optimal. In practice this does not lead to higher CPU temperatures. Even when you think that you're not running any program, you're running OS shell which is actually taking up all CPU resources available. On older operating systems, like various versions of DOS, there is only one process running at a time and we don't have "task manager" because there's no need for it since you can run only one program at a time*. ![]() ![]() That is completely normal because some processes simply have no need for extra CPU time as they could be waiting for something else. So what task manager shows when showing you the CPU load is actually the percentage of time during which the system idle process is not executing. Modern operating systems have things like task schedulers which rotate programs which are executing on the CPU so some percent of the time CPU may not be doing any productive work (for example executing NOPs, jumping in place or whatever the system idle process does). ![]() In some cases it may be shut down to save power. CPU is always running at 100% capacity if it's running at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |