Commit 72b5ee59 authored by Bob Van Landuyt's avatar Bob Van Landuyt

Update the job scheduling and execution targets

This updates the scheduling and execution requirements for jobs based
on the values defined in our metrics catalog:
https://gitlab.com/gitlab-com/runbooks/-/blob/43052e955545046fda35ccc0427193ddae34acae/metrics-catalog/services/lib/sidekiq-helpers.libsonnet#L25-38
parent 7618cb15
...@@ -175,9 +175,9 @@ Jobs can have an `urgency` attribute set, which can be `:high`, ...@@ -175,9 +175,9 @@ Jobs can have an `urgency` attribute set, which can be `:high`,
| **Urgency** | **Queue Scheduling Target** | **Execution Latency Requirement** | | **Urgency** | **Queue Scheduling Target** | **Execution Latency Requirement** |
|--------------|-----------------------------|------------------------------------| |--------------|-----------------------------|------------------------------------|
| `:high` | 100 milliseconds | p50 of 1 second, p99 of 10 seconds | | `:high` | 10 seconds | p50 of 1 second, p99 of 10 seconds |
| `:low` | 1 minute | Maximum run time of 1 hour | | `:low` | 1 minute | Maximum run time of 5 minutes |
| `:throttled` | None | Maximum run time of 1 hour | | `:throttled` | None | Maximum run time of 5 minutes |
To set a job's urgency, use the `urgency` class method: To set a job's urgency, use the `urgency` class method:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment