Skip to content

Commit 93f3146

Browse files
xamberlaowen-uwmad
andauthored
Apply suggestions from code review
Co-authored-by: Andrew Owen <[email protected]>
1 parent b9fdbd5 commit 93f3146

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

_uw-research-computing/variable-memory.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,13 @@ If your job has ever gone on hold for exceeding memory use, you've probably solv
2424

2525
## Why you should care about memory usage
2626

27-
* **Over-requesting memory** may cause your jobs to **wait in idle** for longer than needed, since HTCondor needs to find and allocate these larger resource requests for your jobs. Additionally, CHTC's HTC system is a shared resource, so we encourage you to be a good citizen and only request the resources you need for your jobs.
27+
Because CHTC is a shared resource, correctly requesting the resources that you require for your jobs to function ensures that both you and other users have a good experience on the system.
2828

29-
* **Under-requesting memory** may cause your jobs to **go on hold** when they do exceed the memory allocated to your job.
29+
* **Over-requesting memory** may cause your jobs to **wait in idle** for longer than needed, since HTCondor needs to find and allocate these larger resource requests for your jobs. And resources unused by your job could be used for others' jobs.
3030

31-
> But what if a fraction of your jobs needs more memory than the rest of the list of jobs? How can you get the throughput you need without over-requesting memory?
31+
* **Under-requesting memory** may cause your jobs to **go on hold** when they do exceed the memory allocated to your job. Whatever work by your job will be lost but the computing time will still affect your priority.
32+
33+
But what if only a **fraction** of your jobs needs more memory than the rest of the list of jobs? How can you get the throughput you need without over-requesting memory?
3234

3335
## Use `retry_request_memory`
3436

@@ -59,7 +61,7 @@ retry_request_memory = RequestMemory*4
5961
When using expressions:
6062

6163
* We recommend *only* multiplying by integers.
62-
* Addition expressions and floating point numbers are not recommended.
64+
* Expressions using addition operators or floating point numbers are not recommended.
6365

6466
## Related pages
6567

0 commit comments

Comments
 (0)