[WIP] Mpi-Pingpong Benchmark

[michaelmckinsey1]

Description

• Add MPI pingpong benchmark to benchpark.

• Figure out how to pass location of pingpong directory (since private repo) on command line, instead of hard coding Waiting for repo to be public so we can change the url to point at public repo

• Set number of nodes instead of setting total ranks per machine

• Set required variables for benchpark analyze

  benchpark/experiments/kripke/experiment.py

  Lines 141 to 145 in 95b4534

  	self.set_required_variables(
  	n_resources="{npx}*{npy}*{npz}",
  	process_problem_size="{nzx}*{nzy}*{nzz}/({npx}*{npy}*{npz})",
  	total_problem_size="{nzx}*{nzy}*{nzz}",
  	)

• Depends on Use different value for placeholder instead of relying on max value #957

Adding/modifying a system (docs: Adding a System)

• Update llnl-*/system.py with sys_sockets_per_node parameter

Adding/modifying a benchmark (docs: Adding a Benchmark)

• Add mpi-pingpong benchmark

[michaelmckinsey1]

Running trials in the same allocation parameter (ramble) https://ramble.readthedocs.io/en/latest/workspace_config.html#experiment-repeats

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.08%. Comparing base (b1e3ac4) to head (e2b7332).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #726   +/-   ##
========================================
  Coverage    65.08%   65.08%           
========================================
  Files           44       44           
  Lines         3148     3148           
  Branches       237      237           
========================================
  Hits          2049     2049           
  Misses        1092     1092           
  Partials         7        7           

Files with missing lines	Coverage Δ
systems/llnl-elcapitan/system.py	39.20% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.