Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/rust-performanceEngenharia reversa e 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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/rust-performance

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
zW+oMcsqWg…dzrKpgDg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote818635e3…e0d1c8cb
818635e3c0b3…77fee0d1c8cb6 arquivos · ⁦9.6 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/rust-performance@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd568818635e3Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login