Skip to content

Commit

Permalink
docs: correct the dominator of memory and examples in resource-durati…
Browse files Browse the repository at this point in the history
…on.md (argoproj#11449)

Signed-off-by: Jay Lee <jayin920805@gmail.com>
Signed-off-by: 李杰穎 (Jay Lee) <jayin920805@gmail.com>
Co-authored-by: Anton Gilgur <4970083+agilgur5@users.noreply.github.com>
  • Loading branch information
jayin92 and agilgur5 authored Jul 25, 2023
1 parent 336d8a4 commit 8c3b17a
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions docs/resource-duration.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,5 +53,9 @@ GPU: 3min * 1 / 1 = 3min * (1 nvidia.com/gpu)
Both the web and CLI give abbreviated usage, like `9m10s*cpu,6s*memory,2m31s*nvidia.com/gpu`. In
this context, resources like `memory` refer to the "base amounts".

For example, `memory` means "amount of time a resource requested 1Gi of memory." If a container only
uses 100Mi, each second it runs will only count as a tenth-second of `memory`.
For example, `memory` means "amount of time a resource requested `100Mi` of memory." If a container only
uses `10Mi`, each second it runs will only count as a tenth-second of `memory`.

## Rounding Down

For a short running pods (<10s), if the memory request is also small (for example, `10Mi`), then the memory value may be 0s. This is because the denominator is `100Mi`.

0 comments on commit 8c3b17a

Please sign in to comment.