![]() This means that the actual thread(s) of an application might get swapped around to non-overclocked cores, and even under-clocked cores in some cases. Yes, this is in contrast to the popular fallacy that the single thread would stay on a single core. Normally as a thread gets a time slice (a period in which to use the core), it is granted whichever core is determined to be most free by the operating system’s scheduler. The development of this emerging feature in CPU hardware means that what CPU affinity you set may actually make a big difference in real-world performance. Some newer processors, both AMD (TurboCore) and Intel (TurboBoost), have frequency scaling technologies that allows for scaling up of specific cores on-demand. Remember, the OS CPU scheduler itself will work-around any busy cores, so you need not worry too much about putting too much on too few cores, *but* you should be careful not to under-utilize your computing capacity. You can do this with Process Lasso, using any of three automation features: It is *not* recommended for system components, security software, or other critical services. However, this is an effective method to limit an application’s CPU use. It is hard to say, and varies for each CPU. The computational capacity limits are actually staggered, so they might instead be: 25%, 32%, 82%, 100%. While the scheduler may show an exact 50% for 2 of 4 logical cores, that may not mean those two cores are executing at 50% the capacity of two physical cores. Now, when you throw in logical processors, the picture gets more complex. ![]() Thus, you can keep it at an increment of 25%, 50%, 75%, or 100% for a fully (all physical) quad-core processor. ![]() By limiting a process to specific cores, you have the ability to control the available CPU time it has access to, out of the total CPU time pool. Specifically, keeping a process limited to using a certain amount of CPU time or percent of the total available. One common case where CPU affinity matters is one of CPU resource allocation. When CPU affinity matters Case 1: Limit a Process’s CPU Consumption ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |