TL;DR: when using only 2 or 4 out of 8 total cores, the virtualized
gizmo manages better memory locality and better cache usage because
of less motion of processes to different cores. In HPC, we generally
lock processes to cores, and they should done this, too.
Even shorter: Pilot error, nothing t
On 08/14/2013 03:10 PM, Douglas Eadline wrote:
>
> "When Virtualized HPC Speeds Past Bare Metal"
>
>http://insidehpc.com/2013/08/14/when-virtualized-hpc-speeds-past-bare-metal
>
> Darn, I wish I had that secret virtual sauce, but I am stuck
> with that slow inefficient bare metal. However, I am
"When Virtualized HPC Speeds Past Bare Metal"
http://insidehpc.com/2013/08/14/when-virtualized-hpc-speeds-past-bare-metal
Darn, I wish I had that secret virtual sauce, but I am stuck
with that slow inefficient bare metal. However, I am going to
look into virtualizing the virtualized layer
so t
