Thanks that was helpful. Now I can call my component.
-Manjunath
Tim Prins wrote:
Hi,
In the configure output, there should be a section like:
--- MCA component mtl: (m4 configuration macro)
checking for MCA component mtl: compile mode... dso
checking usability... yes
checking if MCA compo
Jeff Squyres wrote:
I think Terry was asking about running at larger scale on a regular
basis for correctness testing (i.e., nightly snapshot tarballs via MTT).
I was even hoping for a not so regular basis like when certain people go
down to Sandia to see if they
can start up an np=4096 jo
Yes, my point was any testing I do isn't in the form of our usual test
suites. I would like get MTT rolling at some point at LLNL; though I
have (too many :() higher priorities. Also I'm not sure of the 'their
cost' vs. 'our value' ratio of doing runs at much more than 1024 procs
(or even tha
I think Terry was asking about running at larger scale on a regular
basis for correctness testing (i.e., nightly snapshot tarballs via MTT).
I, for one, would love to see the labs run some of our nightly
tarballs at larger scale so that we have a more consistent datapoint
of what "works" an
I won't speak for the labs as a whole, but I generally don't run things
at scale unless theres something specific I'm after, ie benchmarks or
apps I'm using as a benchmark, rather than test suites.
You might look at some of the purple benchmarks:
http://www.llnl.gov/asci/platforms/purple/rfp/b
What about Sandia and LANL? Is there anything that is ran on their
large clusters to confirm things seem to work at high np's?
--td
Jeff Squyres wrote:
Cisco is not yet testing that large, but we plan to shortly start
testing at np>=128 (I'm waiting for an internal cluster within Cisco
to
