On Apr 22, 2015, at 1:57 PM, Jerome Vienne <vien...@tacc.utexas.edu> wrote: > > While looking at performance and control variables provided by the MPI_T > interface, I was surprised by the impressive number of control variables > (1,087 if I am right (with 1.8.4)) but I was also disappointed to see that I > was able to get only 2 performance variables.
Yeah, those were mostly added as "make sure we have the MPI_T Pvar stuff implemented correctly." > I would to know if you are planning to add more Performance variables like > number of time an algorithm from a collective was called, or the number of > buffer allocated/free etc… We're open to adding lots of them. We're actually waiting for specific requests, to be honest. Can you provide a specific list of pvars that you'd like to see? We're also contemplating rolling our existing PERUSE implementation (i.e., a prior generation performance variable system) into the official MPI_T system. It's not immediately clear how to do this, though -- PERUSE and MPI_T aren't 100% compatible. So we've been loosely discussing how to do that (because we *do* have a bunch of MPI_t-performance-variable-like entities under our PERUSE). > Regarding collective tuning, I was wondering if you can recommend me a > paper/presentation that will provide most of the details. I found some > interesting posts (like this one: > http://www.open-mpi.org/community/lists/users/2014/11/25847.php) but I am > looking for a paper/doc explaining the different modules (basic, tuned, self, > hierarchical…) and how to set dynamic rules George: can you provide insight here? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
