g1-tuning-for-slo SKILL.md skillA
g1-tuning-for-slo from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/g1-tuning-for-slo@git:20261028.082d2f4Pins git:20261028.082d2f4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/g1-tuning-for-slo/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.082d2f4, committed Oct 28, 2026
- First version recorded
- Sep 6, 2026
- Size
- 14,463 bytes
- Repository stars
- 3
- License
- Apache-2.0
Deriving G1 flag values from a latency SLO and proving they helped: what `MaxGCPauseMillis` actually controls, the young size bounds, IHOP and adaptive IHOP with an explicit safety margin, region size as the basis of every region-denominated calculation, `G1OldCSetRegionThresholdPercent` and `G1MixedGCCountTarget`, and the measure-derive-predict-validate loop. Use when GC flags were copied from another service, when `-Xms` differs from `-Xmx` in production, when mixed GC violates the SLO while…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# G1 Tuning For SLO ## Purpose Derive candidate G1 flag values from a stated latency SLO, with a traceable measurement behind each one, and test whether the change helped. Every flag in this space moves the system inside a fixed triangle of pause, throughput and footprint — none of them removes the trade-off, so a change without a recorded trade-off is a change nobody can defend. The failure this prevents is tuning by transplant. Two services with the same SLO need different G1 configurations when their allocation rate, promotion rate or average object size differ. A configuration that "worked" elsewhere is at best a starting point for measurement, and at worst hides the actual cause behind a symptom that moved. ## Workflow 1. **Reuse the stated SLO, workload and deployment context.** Confirm the request population, clock, success/error treatment, threshold and window, plus CPU/memory budgets and the actual JDK vendor/update, collector and flags. Preserve the project's target; the implementation examples here use HotSpot JDK 25. Retain an adequate configuration; a flag change is not …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/g1-tuning-for-slo@sha256:5f0ac0acd7322b98The line at the top of this page pins the label git:20261028.082d2f4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uf5hazwb5w7djqlt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 28, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.082d2f4 latest | 2026-10-28 | 082d2f4 | 14,463 B | A | view · diff |
| git:20261016.c769bd8 | 2026-10-16 | c769bd8 | 14,391 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 14,183 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 13,910 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 12,596 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14463 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uf5hazwb5w7djqlt GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/g1-tuning-for-slo GET https://markdownregistry.com/api/v1/blob/5f0ac0acd7322b98aea62ae78e7c19fd1cec74297821c97724e9de1b93c7a5b8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.