Differences

This shows you the differences between two versions of the page.

--- wiki:workaround_for_bug_41288_-_performances_controlling_numa_core_operation [2016/12/01 10:28] – walkeradmin
+++ wiki:workaround_for_bug_41288_-_performances_controlling_numa_core_operation [2023/03/09 22:35] (current) – external edit 127.0.0.1
@@ Line 16: / Line 16: @@
 \\
 If the NUMA Node is set to <color red>false</color>, then this will allow a service to use both NUMA Nodes (so both CPUs, and all memory). This is important if a service has a lot of components (say an ABR service with a lot of profiles) that could be too much for a single processor to handle.
+\\
+\\
+<color red>When setting NUMA to false, you might get a performance improvement if you set the NUAM to of in the BIOS</color>
 \\
 \\
@@ Line 21: / Line 24: @@
 \\
 \\
-{{:wiki:numa_cores_htop_001.png?800|}}
+{{:wiki:numa_cores_htop_0001.jpg?800|}}
 \\
 \\
@@ Line 27: / Line 30: @@
 \\
 \\
-{{:wiki:numa_cores_htop_002.png?800|}}
+{{:wiki:numa_cores_htop_0002.jpg?800|}}
 \\
 \\
@@ Line 43: / Line 46: @@
 \\
 \\
+----
+==== Processor Occupancy ====
+\\
+We know that there are many cores (CPUs) per socket, and these cores are allocated by the operating system. However the allocation of processor cores isn't actually that random.
+\\
+\\
+{{:wiki:processor_order_slope.jpg?200|}}
+\\
+\\
+The diagram above shows one of the NUMA cores, and it can be seen that the cores are used in order, and that core 1 is always the most used core, while the lower cores may get only the occasional use. This of course doesn't mean much, but it is interesting to know.
+\\
+\\
+<color red>When setting NUMA to false, you might get a performance improvement if you set the NUMA to off in the BIOS</color>
+\\
+\\