[ET Trac] [Einstein Toolkit] #1865: Automatically start SystemTopology
Einstein Toolkit
trac-noreply at einsteintoolkit.org
Mon Oct 3 10:54:16 CDT 2016
#1865: Automatically start SystemTopology
----------------------------------+-----------------------------------------
Reporter: dradice@… | Owner: eschnett
Type: enhancement | Status: reopened
Priority: major | Milestone:
Component: Carpet | Version: development version
Resolution: | Keywords:
----------------------------------+-----------------------------------------
Comment (by eschnett):
SystemTopology can check, but that's dangerous. What if it decides that
you're not running on a "full node" simply because it counts cores
differently from what the user expects? If you read the documentation for
Blue Waters, you'll see that not even NCSA could agree with itself on how
many cores a node has. (Slurm, MPI, and the accounting system use
different core counts.) What if you run in a virtual machine or a Docker
environment? What if you run on a workstation, and by chance are using all
cores, while there is also a second Cactus job running?
In my view, the default behaviour should do the right thing for the
unsuspecting user. Experts can be expected to put in a bit more effort,
e.g. changing a line in the scripts they use to submit jobs.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1865#comment:12>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
More information about the Trac
mailing list