-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All PaRSEC threads binding to the same physical core #130
Comments
The bind-to none option is passed to Open MPI or parsec? Parsec should
ignore the existing binding of MPI iirc and use all cores by default... Can
you post your command and configuration?
…On Sat, Jul 31, 2021, 08:57 Joseph John ***@***.***> wrote:
Hi,
When am running a TTG program all the thread gets bound to the same
physical core. Things are working better when I use
--bind-to none
Are there any performance problems if I use --bind-to none. Program was
compiled using the following modules.
intel-mkl/2021.2.0 boost/1.71.0 openmpi/4.0.2 eigen/3.3.7 libunwind/1.2.1 intel-compiler/2021.2.0
Regards,
Joseph
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#130>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACTXKJVCBBOIFPHBCF4QRJDT2P6LNANCNFSM5BKBPZFQ>
.
|
The bind-to none option was passed to mpi. This was the pbs script I used initially where all the threads were getting bound to the same physical core and the job was getting timed out.
When I added --bind-to none the run is complete in 90sec.
I am running with one mpi process per node. PaRSEC was build normally without any additional features and this external PaRSEC was used to build TTG.
|
Any chance your PaRSEC wasn't built with support for hwloc? According to the OMPI documentation, the default binding with np<=2 is |
PaRSEC was built with hwloc. ldd libparsec.so.3.0.0 gives the following
|
This is the error generated by PaRSEC ^[[1;37;43mW@00000^[[0m binding core #2000 not valid (must be between 0 and 47 (nb_core-1) |
Hi,
When am running a TTG program all the thread gets bound to the same physical core. Things are working better when I use
Are there any performance problems if I use --bind-to none?
Program was compiled using the following modules- intel-mkl/2021.2.0 boost/1.71.0 openmpi/4.0.2 eigen/3.3.7 libunwind/1.2.1 intel-compiler/2021.2.0
and I am working the parsec commit 15b871975fa596e1f2d5e4430c405d9e1b50e54d.
Regards,
Joseph
The text was updated successfully, but these errors were encountered: