Skip to content

Commit

Permalink
Merge pull request #657 from lbarraga/faq-typos
Browse files Browse the repository at this point in the history
typo fixes FAQ
  • Loading branch information
boegel authored Aug 19, 2024
2 parents 93e3a73 + 78d4e07 commit bd86bc2
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions mkdocs/docs/HPC/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Overview of HPC-UGent Tier-2 [infrastructure]({{ hpc_infrastructure_url }})

### How many cores/nodes should I request?

An important factor in this question is how well your task is being parallellized:
An important factor in this question is how well your task is being parallelized:
does it actually run faster with more resources? You can test this yourself:
start with 4 cores, then 8, then 16... The execution time should each time be reduced to
around half of what it was before. You can also try this with full nodes: 1 node, 2 nodes.
Expand Down Expand Up @@ -171,7 +171,7 @@ Not all file locations perform the same. In particular, the `$VSC_HOME` and `$VS
directories are, relatively, very slow to access. Your jobs should rather use the
`$VSC_SCRATCH` directory, or other fast locations (depending on your needs), described
in [Where to store your data on the HPC](../running_jobs_with_input_output_data/#where-to-store-your-data-on-the-hpc).
As an example how do this: The job can copy the input to the scratch directory, then execute
As an example how to do this: The job can copy the input to the scratch directory, then execute
the computations, and lastly copy the output back to the data directory.
Using the home and data directories is especially a problem when UGent isn't your home institution:
your files may be stored, for example, in Leuven while you're running a job in Ghent.
Expand Down Expand Up @@ -217,12 +217,13 @@ See the explanation about how jobs get prioritized in [When will my job start](.

{% else %}

In practice it's
In practice, it's
impossible to predict when your job(s) will start, since most currently
running jobs will finish before their requested walltime expires, and
new jobs by may be submitted by other users that are assigned a higher
priority than your job(s). You can use the `showstart` command. For more
information, see .
running jobs will finish before their requested walltime expires.
New jobs may be submitted by other users that are assigned a higher
priority than your job(s).
You can use the `squeue --start` command to get an estimated start time for your jobs in the queue.
Keep in mind that this is just an estimate.

{% endif %}

Expand Down

0 comments on commit bd86bc2

Please sign in to comment.