golang-performance
Go performance workflow: benchmark and profile (pprof/trace), identify hotspots, reduce allocations/GC and contention, and verify improvements with repeatable measurement. Use only after you have evidence the Go code is the bottleneck.
v2026.11.13-21cd5683 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 11 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/golang-performanceEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete6cc84c1b…44f627ba
6cc84c1bb58f…733d44f627ba6 archivos · 9.7 KBEscaneoMedio9 hallazgos
- Enlace a una IP directareferences/compiler-and-runtime-tuning.md:103
- Enlace a una IP directareferences/profiling.md:43
- Enlace a una IP directareferences/profiling.md:55
Fuentegithub.com/AeonDave/malskill/tree/main/coding/golang-performance@21cd568
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
This skill is about measurement-first optimization in Go.
When to activate
Use this skill when you need to:
- Confirm a performance regression (latency/throughput/CPU/memory)
- Identify hot paths with pprof (CPU / heap / mutex / block)
- Reduce allocations and GC pressure in a measured hotspot
- Fix contention (mutex, scheduler, channel backpressure)
- Validate improvements with benchmarks and repeatable runs
If you need general idioms and patterns (not measurement), use golang-patterns.
Rules of engagement
- Profile before optimizing. A fast guess beats a slow change.
- Change one thing at a time. Measure after each change.
- Keep a baseline. Every claim should have “before vs after”.
- Don’t optimize the cold path. Make the hot path boring.
Outcome expectations
- Performance claims are backed by reproducible before/after measurements.
- Profile type selection matches the observed symptom.
- Optimizations are incremental, attributable, and regression-resistant.
Workflow
Make it measurable
- Add a benchmark (or a reproducible load test) for the suspected hotspot.
- Run multiple iterations; record mean + variance.
Capture evidence
- CPU profile for time
- Heap/allocs profile for memory
- Mutex/block profiles for contention
- Trace when the scheduler / GC behavior matters
Analyze before changing code
- Identify top offenders (
top,top -cum) - Inspect annotated source (
list) - Confirm whether you are bound by CPU, allocations, syscalls, or contention
- Identify top offenders (
Apply targeted fixes
- Allocation and GC: reduce allocations, reuse buffers, avoid retaining large backing arrays
- Data layout: improve locality, avoid interface boxing in hot loops
- Concurrency: reduce contention, bound goroutines, add backpressure
Verify and document
- Re-run the benchmark/profile
- Ensure correctness isn’t traded away
- Record the change and its measured impact
Symptom to first profile mapping
- High CPU -> CPU profile
- Memory growth -> heap profile (compare snapshots)
- High allocation churn / GC pressure -> allocs profile
- Latency spikes without CPU spike -> block profile
- Lock contention suspicion -> mutex profile
- Scheduler/pathological latency behavior -> runtime trace (flight recorder for rare events)
- Growing goroutine count / suspected stuck workers ->
goroutineleakprofile, then the full goroutine profile - Shipped binary that is already profile-tuned and needs final runtime/build tuning ->
compiler-and-runtime-tuning.md
Safety note: exposing pprof
net/http/pprof endpoints can leak sensitive runtime data. Prefer:
- bind to
localhost - protect with auth / firewall
- enable only in dev / controlled environments
Resources
Load these references on demand:
references/profiling.md— pprof + trace (HTTP andgo testcapture) +goroutineleak+ flight recorderreferences/benchmarks.md— stable benchmarks, -benchmem, benchstat, hygienereferences/allocations-gc.md— allocation patterns, Green Tea GC, slice retention, sync.Poolreferences/contention.md— mutex/block profiles, contention patterns, backpressurereferences/compiler-and-runtime-tuning.md— load when code-level fixes have landed and you need PGO, GOGC/GOMEMLIMIT, GOMAXPROCS/cgroup, GC/cgo/thread knobs, or shipped-binary build flags
Archivos de esta versión
references/518.4 KB
- allocations-gc.md2.9 KB
- benchmarks.md2.1 KB
- compiler-and-runtime-tuning.md7.7 KB
- contention.md1.4 KB
- profiling.md4.3 KB
- SKILL.md4.0 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | Sí | Sí |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaEnlace · Enlace a una IP directareferences/compiler-and-runtime-tuning.md:103
- MediaEnlace · Enlace a una IP directareferences/profiling.md:43
- MediaEnlace · Enlace a una IP directareferences/profiling.md:55
- MediaEnlace · Enlace a una IP directareferences/profiling.md:56
- MediaEnlace · Enlace a una IP directareferences/profiling.md:74
- MediaEnlace · Enlace a una IP directareferences/profiling.md:75
- MediaEnlace · Enlace a una IP directareferences/profiling.md:94
- MediaEnlace · Enlace a una IP directareferences/profiling.md:110
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 6cc84c1b | Firmada | – |
Más de AeonDave
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login