Re: [OMPI users] Q: Binding to cores on AWS?

Hi Gilles, You're right, we no longer get warnings... and the performance disparity still exists, though to be clear it's only in select parts of the code - others run as we'd expect. This is probably why I initially guessed it was a process/memory affinity issue - the one timer I looked at is

Re: [OMPI users] Q: Binding to cores on AWS?

Brian, i have no doubt this was enough to get rid of the warning messages. out of curiosity, are you now able to experience performances close to native runs ? if i understand correctly, the linux kernel allocates memory on the closest NUMA domain (e.g. socket if i oversimplify), and since MPI

Re: [OMPI users] Q: Binding to cores on AWS?

Hi Ralph, Well, this gets chalked up to user error - the default AMI images come without the NUMA-dev libraries, so OpenMPI didn't get built with it (and in my haste, I hadn't checked). Oops. Things seem to be working correctly now. Thanks again for your help, - Brian On Fri, Dec 22,

Re: [OMPI users] Q: Binding to cores on AWS?

I honestly don’t know - will have to defer to Brian, who is likely out for at least the extended weekend. I’ll point this one to him when he returns. > On Dec 22, 2017, at 1:08 PM, Brian Dobbins wrote: > > > Hi Ralph, > > OK, that certainly makes sense - so the next

Re: [OMPI users] Q: Binding to cores on AWS?

Hi Ralph, OK, that certainly makes sense - so the next question is, what prevents binding memory to be local to particular cores? Is this possible in a virtualized environment like AWS HVM instances? And does this apply only to dynamic allocations within an instance, or static as well?

Re: [OMPI users] Q: Binding to cores on AWS?

Actually, that message is telling you that binding to core is available, but that we cannot bind memory to be local to that core. You can verify the binding pattern by adding --report-bindings to your cmd line. > On Dec 22, 2017, at 11:58 AM, Brian Dobbins wrote: > > >

[OMPI users] Q: Binding to cores on AWS?

Hi all, We're testing a model on AWS using C4/C5 nodes and some of our timers, in a part of the code with no communication, show really poor performance compared to native runs. We think this is because we're not binding to a core properly and thus not caching, and a quick 'mpirun --bind-to

Re: [hwloc-users] pianofish process management GUI

In the top-level README.md of the python-hwloc source at https://gitlab.com/guystreeter/python-hwloc.git I've added examples of doing a pip install from a clone of the git tree. I'll look into getting it into pypi, but I'd like to know if the pip install from source works on other distros. --Guy