From 64e034aed1c492dba5ff5492d04e731f26673fe7 Mon Sep 17 00:00:00 2001 From: Trevor Keller Date: Thu, 19 Jan 2023 15:58:27 -0500 Subject: [PATCH] see amdahl not cpi in history --- _episodes/17-resources.md | 10 +++++----- .../NIST_CTCMS_slurm/resources/account-history.snip | 8 ++++---- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/_episodes/17-resources.md b/_episodes/17-resources.md index 493a66ab..61359428 100644 --- a/_episodes/17-resources.md +++ b/_episodes/17-resources.md @@ -47,9 +47,9 @@ finish and free up the resources needed to match what you asked for. ## Stats -Since we already submitted `pi.py` to run on the cluster, we can query the +Since we already submitted `amdahl` to run on the cluster, we can query the scheduler to see how long our job took and what resources were used. We will -use `{{ site.sched.hist }}` to get statistics about `parallel-pi.sh`. +use `{{ site.sched.hist }}` to get statistics about `parallel-job.sh`. ``` {{ site.remote.prompt }} {{ site.sched.hist }} @@ -87,12 +87,12 @@ keys to scroll through fields). ## Improving Resource Requests -From the job history, we see that `pi.py` jobs finished executing in +From the job history, we see that `amdahl` jobs finished executing in at most a few minutes, once dispatched. The time estimate we provided in the job script was far too long! This makes it harder for the queuing system to accurately estimate when resources will become free for other jobs. Practically, this means that the queuing system waits -to dispatch our `pi.py` job until the full requested time slot opens, +to dispatch our `amdahl` job until the full requested time slot opens, instead of "sneaking it in" a much shorter window where the job could actually finish. Specifying the expected runtime in the submission script more accurately will help alleviate cluster congestion and may @@ -100,7 +100,7 @@ get your job dispatched earlier. > ## Narrow the Time Estimate > -> Edit `parallel_pi.sh` to set a better time estimate. How close can +> Edit `parallel_job.sh` to set a better time estimate. How close can > you get? > > Hint: use `{{ site.sched.flag.time }}`. diff --git a/_includes/snippets_library/NIST_CTCMS_slurm/resources/account-history.snip b/_includes/snippets_library/NIST_CTCMS_slurm/resources/account-history.snip index 1fd637fa..61ac15e5 100644 --- a/_includes/snippets_library/NIST_CTCMS_slurm/resources/account-history.snip +++ b/_includes/snippets_library/NIST_CTCMS_slurm/resources/account-history.snip @@ -6,11 +6,11 @@ 212341 env {{ site.sched.queue.debug }} 2 COMPLETED 212342 mpirun {{ site.sched.queue.testing }} 2 COMPLETED 212343 mpirun {{ site.sched.queue.testing }} 2 COMPLETED -212344 cpi {{ site.sched.queue.testing }} 2 COMPLETED -212345 cpi {{ site.sched.queue.testing }} 2 COMPLETED +212344 amdahl {{ site.sched.queue.testing }} 2 COMPLETED +212345 amdahl {{ site.sched.queue.testing }} 2 COMPLETED 212346 bash {{ site.sched.queue.testing }} 2 COMPLETED 212346.0 bash 2 COMPLETED -212346.1 cpi 2 COMPLETED -212347 cpi {{ site.sched.queue.testing }} 2 FAILED +212346.1 amdahl 2 COMPLETED +212347 amdahl {{ site.sched.queue.testing }} 2 FAILED ``` {: .output}