You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GlobalTemplateDiskBufferfloat64`yaml:"global_template_disk_buffer"`// Global disk buffer percentage (e.g., 10.0 for 10%)
43
+
GlobalSkipCPUAndMemoryResourceChecksbool`yaml:"global_skip_cpu_and_memory_resource_checks"`// Global override to skip CPU/RAM resource admission checks
Copy file name to clipboardExpand all lines: plugins/handlers/github/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ plugins:
38
38
# registration_timeout_seconds: 80 # Optional; defaults to 80 seconds.
39
39
# template_disk_buffer: 10.0 # Optional; defaults to 10.0%. How much disk space to leave free on the host for templates.
40
40
# job_retry_attempts: 10 # Override the default of 5
41
+
# skip_cpu_and_memory_resource_checks: true # Optional; allows CPU/RAM overcommit by skipping VM admission checks on this host.
41
42
#database:
42
43
# enabled: true
43
44
# url: localhost
@@ -57,6 +58,7 @@ plugins:
57
58
- If you are attempting to register runners for an entire organization, do NOT set `repo` and make sure your Github App has `Self-hosted runners` > `Read and write` permissions.
58
59
- If your Organization level runner is registered and your public repo jobs are not picking it up even though the labels are a perfect match, make sure the Runner groups (likely `Default`) has `Allow public repositories`.
59
60
- There are times when github will not register the runner for some reason. `registration_timeout_seconds` is available to set the custom seconds to wait before considering the runner registration failed (and retry on a new VM).
61
+
-`skip_cpu_and_memory_resource_checks` (or global `global_skip_cpu_and_memory_resource_checks`) is intended for overcommit fleets. It allows multiple VMs to start even when host CPU/RAM capacity checks would normally block them, which can improve throughput in bursty workloads but may increase contention and job runtime variance under sustained load.
0 commit comments