Closing this as it's not a bug in nova-lxd and this is being tracked
elsewhere.
** Changed in: nova-lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639932
Ti
5 core LXD - 10 copies
Benchmark Run: Tue Nov 08 2016 13:54:48 - 14:24:40
5 CPUs in system; running 10 parallel copies of tests
Dhrystone 2 using register variables 164210758.1 lps (10.0 s, 7 samples)
Double-Precision
To confirm, when running with a 5 core LXD container, I only ever see 5
CPU's loading - the other 5 are idle/doing other busy work for the
hosting OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639
It would be good to get the breakdown of those figures - the UnixBench
index is a blend of CPU + other benchmarks, including disk IO, so its
possible that the choke point is not actually the CPU, but some other
resource - for example ran the benchmark with 5 and 10 cpu constrained
LXD instances and
Feedback in regards to why bug has been filed:
UnixBench parallel test final "System Benchmarks Index Score" run as root, on
different size
/flavor instances/containers, with different numbers of "copies" of UnixBench.
instance cores ->
parallel tests
c20 c40
x10 2967.7 2844.6
x20 3802.4 3152.3
x4
