Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/rust-performanceIngeniería inversa y fuzzing

rust-performance

⁨Rust performance workflow: benchmark and profile first, identify hotspots, reduce allocations and contention, improve data layout, tune release profiles, and verify gains with repeatable evidence. Use only after you have a real Rust performance symptom, regression, or hotspot in `.rs` code.⁩

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/rust-performance

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
zW+oMcsqWg…dzrKpgDg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete818635e3…e0d1c8cb
818635e3c0b3…77fee0d1c8cb6 archivos · ⁦9.6 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding/rust-performance@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

This skill is about measurement-first optimization in Rust.

If the task is primarily code style, ownership, or API design, use rust-patterns first.

When to activate

  • Investigating latency, throughput, CPU, memory, or allocation regressions in Rust
  • Benchmarking a hot path before and after a change
  • Hunting down lock contention, slow async pipelines, or poor data layout
  • Tuning release profiles or deciding whether parallelism actually helps

Rules of engagement

  • Measure before changing code. Hot takes are not hot paths.
  • Change one variable at a time. Keep a stable baseline and compare before vs after.
  • Fix algorithm and data-structure issues first, then allocations, then micro-optimizations.
  • Optimize the code you can prove is hot, not the code that merely looks suspicious.
  • Preserve correctness, readability, and maintainability; fast wrong code is still wrong.

Outcome expectations

  • Performance claims are backed by reproducible measurements.
  • Profile data points clearly to one or few prioritized hotspots.
  • Fixes are incremental and attributable (one change, one measurement delta).
  • Correctness and behavior remain unchanged after optimization.

Workflow

  1. Make the problem measurable

    • Define the symptom: latency, throughput, CPU, heap, alloc count, lock wait, or tail latency.
    • Add a benchmark or a reproducible workload before touching the implementation.
  2. Capture evidence

    • CPU profile for time spent
    • Allocation / heap profile for churn and retention
    • Contention evidence for locks, channels, or task scheduling
  3. Analyze the bottleneck

    • Confirm whether the problem is algorithmic, allocation-heavy, cache-unfriendly, or synchronization-heavy.
    • Inspect the hottest call paths before proposing fixes.
  4. Apply targeted fixes

    • Pre-allocate, reuse buffers, remove needless clones, tighten data layout, or reduce synchronization.
    • Add parallelism only when the workload is large enough and coordination cost is justified.
  5. Verify the result

    • Re-run the same benchmark/profile
    • Record the measurable improvement and ensure behavior is unchanged

Symptom to first tool mapping

  • High CPU or low throughput -> Criterion + CPU profiler / flamegraph
  • Memory growth or heap churn -> allocation/heap profiler (dhat, heaptrack)
  • Latency spikes with shared state -> contention and lock analysis
  • Async scheduling inefficiency -> runtime-aware tracing and task instrumentation
  • CI performance regressions -> deterministic instruction-count benchmarking (iai-callgrind)
  • Shipping a binary that is already profile-tuned and needs final codegen/build tuning -> build tuning (compiler-and-build-tuning.md)

Resources

Load on demand:

  • references/measurement-workflow.md — use when defining benchmarks, baselines, and release settings
  • references/profiling.md — use when choosing CPU, heap, allocation, or contention profilers
  • references/allocations-and-data-layout.md — use when the bottleneck smells like cloning, heap churn, or cache locality
  • references/concurrency-and-throughput.md — use when evaluating Rayon, async throughput, locks, channels, backpressure, available_parallelism, or false sharing
  • references/compiler-and-build-tuning.md — use when release-profile knobs are not enough, or when tuning -C target-cpu, PGO, BOLT, LLD, --timings, or nightly Cranelift / parallel frontend

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd568818635e3Firmada–

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. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login