proomt

Search

Search posts, papers, and topics

All posts

Lobsters4 min readintermediate

Benchmarking Wild vs Mold

Read on github.ioHN 46·1 commentsLobsters 52

Summary

Reproduces Mold’s linker benchmarks on a 16‑core Ryzen, shows that configuration (filesystem, delete‑output, fork) explains most of the Wild vs Mold speed gap, and notes recent Mold releases and upcoming Wild tweaks that close the gap.

  • Mold’s benchmarks delete the output file and use ext4; Wild’s original benchmarks kept the file on tmpfs – these choices can swing runtimes by ~30 %.
  • Running with `--no‑fork` (Mold default) vs allowing fork (Wild default) also impacts measured time.
  • When both linkers are run with the same ext4+delete+no‑fork setup, Wild is within ~20 % of Mold on the tested benchmarks.
  • Mold’s recent 2.42.x releases delivered a noticeable speedup, narrowing the gap with Wild’s August 4th numbers.

Linker speed directly affects developer iteration time for large C/C++/Rust codebases. Understanding benchmark methodology prevents misleading performance claims and guides contributors on where to focus optimizations.

7/10
performancesystems programminglinuxbenchmarklinker

Related reading

  1. SiliconBench: Speed, Memory, and Fidelity for LLM Serving on Unified-Memory Desktops

    SiliconBench benchmarks nine Apple‑Silicon LLM serving engines on unified‑memory desktops, measuring speed, memory usage, and output fidelity across Qwen3, Qwen3.5, and Gemma‑4 models. It finds vllm‑metal doubles throughput at modest concurrency, memory budgets often fail to preserve headroom, and only three stacks satisfy all fidelity and model‑coverage requirements, with tensor‑parallel scaling…

    Hugging Face Daily Papersarxiv.org1 minpaper

  2. Accurate Models of AMD Matrix Cores

    The authors reverse‑engineer AMD’s CDNA matrix cores, build per‑architecture MATLAB models that match hardware bit‑for‑bit on 10 M random tests, and use them to compare AMD vs NVIDIA tensor‑core accuracy.

    Hacker News front pagearxiv.org2 minpaperHN7911

  3. Migrating the GitHub Copilot runtime to Rust, using Copilot

    The Copilot agent runtime was rewritten from a 130‑k‑line TypeScript/Node.js codebase into a native Rust library (~830 k lines of Rust) to reduce startup latency, memory use, and improve reliability. The migration was done incrementally (in‑place) across 128 PRs, with AI‑generated code handling most of the work. The new runtime exposes a C ABI for in‑process embedding by all six Copilot SDK langu…

    GitHub Oldgithub.blog65 minHN188
  4. 1 points

    Saving another 100TB of RAM with math (and Rust)

    Cloudflare reduced the memory footprint of its Pingora Backend Router by re‑examining the consistent‑hashing implementation in the pingora‑ketama library. By increasing the number of virtual hash points per server from the default 1 to the standard 160 (and applying weighted hashing based on disk capacity), they cut the per‑node overhead enough to reclaim >100 TB of RAM across the fleet. The post…

    Hacker News front pagecloudflare.com13 minHN478120lobste.rs33

  6. Run Terminal-Bench and other Harbor evals on Vercel Sandbox

    Vercel now supports running Harbor benchmarks, like Terminal‑Bench, inside its Sandbox using Firecracker microVMs. The integration with AI Gateway lets you benchmark multiple models by swapping the `--model` flag, scaling concurrency with `--n-concurrent`.

    Vercelvercel.com1 minrelease