Commit 4a3a8a3
committed
CP-53642: change default NUMA placement policy to best-effort
We've seen that using the policy can be up to 10% faster than using any is some
workflows, while not observing workflows that were negatively affected. The
policy per VM can always be change if need be.
Note that currently sometime the best-effort falls back to the same behaviour,
especially when restarting on starting more than one VM at a time. This needs
xen patches to be fixed:
https://lore.kernel.org/xen-devel/[email protected]/T/#ma1246e352ea3cce71c7ddc26d1329a368548b3b2
Now the deprecated numa-placement configuration option for xenopsd does nothing.
It was exclusively used to enable Best_effort, since now it's the default,
there's no point in setting the option. It's value depends on whether the
default option is best_effort or not, as per the spec.
Signed-off-by: Pau Ruiz Safont <[email protected]>1 parent 983a48a commit 4a3a8a3
File tree
3 files changed
+7
-8
lines changed- ocaml/xenopsd
- lib
- xc
3 files changed
+7
-8
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3472 | 3472 | | |
3473 | 3473 | | |
3474 | 3474 | | |
3475 | | - | |
| 3475 | + | |
3476 | 3476 | | |
3477 | | - | |
| 3477 | + | |
3478 | 3478 | | |
3479 | 3479 | | |
3480 | 3480 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
59 | 59 | | |
60 | 60 | | |
61 | 61 | | |
62 | | - | |
63 | | - | |
64 | 62 | | |
65 | 63 | | |
66 | 64 | | |
| |||
242 | 240 | | |
243 | 241 | | |
244 | 242 | | |
245 | | - | |
246 | | - | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
247 | 248 | | |
248 | 249 | | |
249 | 250 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5294 | 5294 | | |
5295 | 5295 | | |
5296 | 5296 | | |
5297 | | - | |
5298 | | - | |
5299 | 5297 | | |
5300 | 5298 | | |
5301 | 5299 | | |
| |||
0 commit comments