-
Notifications
You must be signed in to change notification settings - Fork 11
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
mr_th_nb perfs #1
Comments
@ggouaillardet Thanks for looking into this. My main goal is to see how yalla works. But I was also working with ob1/openib to reproduce results of original request refactoring developers. I'll appreciate if you can test this code and provide the feedback! |
@hjelmn @bosilca @jsquyres, I noticed that sometimes with this benchmark I'm using open-mpi/ompi@267821f as master and open-mpi/ompi-release@87a79f5 as v2.x in case you may be aware of things that may cause this. |
@jsquyres @jladd-mlnx @hppritcha @bosilca Do we want to move this somewhere in OMPI? This is not a production grade but I'm sure we can improve it. @bosilca had some improvement ideas so it makes sense to put it into some public location. |
We can certainly add one more threaded test in the ompi-tests repo. |
@artpol84 i checked the minutes of the telcon, and then checked your benchmark.
are you using
mtl/mxm
orbtl/openib
?in the case of
btl/openib
, i would not expect any gain when increasing the number of threads, since my understanding is btl will serialize send and tag/communicator matching on the receive side.i do not know about
mtl/mxm
, it might be able to do thread parallelism since you are using one tag per thread.@hjelmn @bosilca @jsquyres does this make sense ?
The text was updated successfully, but these errors were encountered: