neo vs Rust · language

neo vs Rust.

The same input and the same kernels, in neo's C++ and in Rust. Across 5 measurements neo finished 1.45× faster in the middle and 2.24× at most; Rust was not quicker on any.

01 · The race

One kernel at a time

Each piece of work below has its own race, what it measures, how each side does it, the code that ran and every number taken for it. In a race both ships run for the same stretch: Rust completes the work once, and neo completes it as many times as the measured ratio says, turning around at each end.

  1. 01.1 · load the CSV, parse and type1.28×
  2. 01.2 · filter amount > 500, count2.24×
  3. 01.3 · sort, as a permutation1.21×
  4. 01.4 · sort into a new table1.45×
  5. 01.5 · sum by region2.20×

01.1 · kernel · 1,000,000 rows

load the CSV, parse and type

neo 3.59 ms · Rust 4.60 ms · 1.28× neo. Against every engine →

neo

Rust

0 runs

0 runs

What this measures

Read a 46 MB CSV of a million rows and six columns into a table: split the bytes into fields, parse the amount column into numbers, and dictionary-encode the region column. Each engine's typed read, best of two, with the first read of a fresh process kept separately.

How neo does it

neo's parser finds the structural characters with SIMD, splits the file into blocks and parses them on every core above a megabyte, with results identical to the serial path. Typing and the dictionary happen once, at load, on the pool, so no kernel after it touches text. In the ledger's breakdown that is 2.8 ms of parse, 0.2 ms of typing and about nothing for the dictionary.

How Rust does it

The port's load is the whole program rather than one function, so it is not excerpted here: neon-cpp/bench/lang/rust/src/main.rs.

neo's side: the call and the contract

the harness, calling the engine · neon-cpp/bench/bench_engine_options.cpp:194
l.t = csv::parse(raw);
the parser's contract · neon-cpp/core/csv.h:55
Table parse(std::string_view raw);  // parallel above 1 MB, serial below; identical results

Every number taken for it

measurementneoRust× neo
time, msThree loads to warm, then three timed whole loads; the median over every timed load of seven shuffled rounds.3.594.601.28×

Read it with this

  • A port builds one dictionary where neo builds three.
  • Taken on a shared machine. Both columns ran in the same shuffled rounds, so the multiple stands, but the times themselves read high.

01.2 · kernel · 1,000,000 rows

filter amount > 500, count

neo 0.017 ms · Rust 0.038 ms · 2.24× neo. Against every engine →

neo

Rust

0 runs

0 runs

What this measures

Count the rows whose amount is over 500: a million comparisons on a typed column, the answer one integer. Each library's count is written the way its users write it.

How neo does it

neo's filter produces a bitmap: one bit per row, 125 KB for a million rows, written at memory speed, with indices made only when something needs them. Below about a million values it runs on one thread, above that on the pool. The contract is the JavaScript node's: NaN never matches.

How Rust does it

Two passes on the pool. Each chunk counts its hits, a running total gives every chunk its own slice of the output, and each chunk then writes its row numbers into that slice.

filter amount > 500 · neon-cpp/bench/lang/rust/src/main.rs:1166
/// Two passes: per-chunk counts, prefix sum, then every chunk writes into its own slice.
fn filter_mt(amt: &[f64], pool: &Pool, parts: usize) -> Vec<u32> {
    let n = amt.len();
    let ranges = chunk_ranges(n, parts);
    let counts: Vec<usize> = pool.map(parts, |p| {
        let (a, b) = ranges[p];
        amt[a..b].iter().map(|&x| (x > 500.0) as usize).sum()
    });
    let mut starts = vec![0usize; parts + 1];
    for p in 0..parts {
        starts[p + 1] = starts[p] + counts[p];
    }
    let total = starts[parts];
    let mut out: Vec<u32> = Vec::with_capacity(total);
    let op = SyncPtr(out.as_mut_ptr());
    pool.run(parts, |p| unsafe {
        let (a, b) = ranges[p];
        let k = filter_range(amt, a, b, op.get().add(starts[p]), counts[p]);
        debug_assert_eq!(k, counts[p]);
    });
    unsafe { out.set_len(total) };
    out
}

neo's side: the call and the contract

the harness, calling the engine · neon-cpp/bench/bench_engine_options.cpp:337
const double f5 = timeIt([&] { Bitmap b = compareDoubles(amt.data(), n, Cmp::Gt, 500, &pool); sink = b.words[0]; }, 7);
the filter's contract · neon-cpp/core/selection.h:1
// selection.h — the result of a filter: one bit per row. 1M rows = 125 KB,
// written at memory speed; indices are produced only when something needs them.

struct Bitmap {
    std::vector<uint64_t> words;
    size_t bits = 0;
    bool test(size_t i) const { return (words[i >> 6] >> (i & 63)) & 1; }
    size_t count() const;
    std::vector<uint32_t> indices() const;  // ascending row indices of the set bits
};

// JS measurefilter semantics: NaN never matches. Sequential below ~1M values; the pool otherwise.
Bitmap compareDoubles(const double* v, size_t n, Cmp op, double threshold, Pool* pool);

Every number taken for it

measurementneoRust× neo
time, msBest of three in one process, then the median over seven rounds, every engine run once a round in a shuffled order.0.0170.0382.24×

Read it with this

  • The two results differ in form: neo's figure is for a bitmap, the port's for a list of row numbers.
  • Taken on a shared machine. Both columns ran in the same shuffled rounds, so the multiple stands, but the times themselves read high.

01.3 · kernel · 1,000,000 rows

sort, as a permutation

neo 1.04 ms · Rust 1.27 ms · 1.21× neo. Against every engine →

neo

Rust

0 runs

0 runs

What this measures

Produce the stable ascending order of the amount column as a permutation of row indices, without moving any other column. SQL engines have no such form, so DuckDB and Spark sit this one out.

How neo does it

neo turns each double into a sortable 64-bit key and runs an LSD radix sort on the pool: O(n), stable, with the JavaScript rule that NaN sorts as negative infinity and ties keep their order. The ledger's design levers show the step from std::stable_sort at 84 ms, to radix at 14 ms, to the pool at 1 ms.

How Rust does it

A radix sort on sortable 64-bit keys. It first finds the highest 16-bit digit in which the keys differ and partitions on that, with a histogram for each part of the input.

sort, as a permutation · neon-cpp/bench/lang/rust/src/main.rs:1549
fn sort_perm_mt(amt: &[f64], pool: &Pool, threads: usize) -> Vec<u32> {
    radix_perm_mt(amt, pool, threads)
}
the radix sort behind it · neon-cpp/bench/lang/rust/src/main.rs:1338 · show all 143 lines
fn radix_perm_mt(amt: &[f64], pool: &Pool, threads: usize) -> Vec<u32> {
    const NB: usize = 1 << 16;
    let prof = PROFILE_SORT.load(Relaxed);
    let t0 = Instant::now();
    let n = amt.len();
    let parts = threads.max(1);
    let ranges = chunk_ranges(n, parts);
    // the highest 16-bit digit in which the keys differ decides the partition digit
    let mm: Vec<(u64, u64)> = pool.map(parts, |q| {
        let (a, b) = ranges[q];
        amt[a..b].iter().fold((u64::MAX, 0u64), |(lo, hi), &x| {
            let k = sortable(x);
            (lo.min(k), hi.max(k))
        })
    });
    let (lo, hi) = mm.iter().fold((u64::MAX, 0u64), |(l, h), &(a, b)| (l.min(a), h.max(b)));
    if lo == hi {
        return (0..n as u32).collect();
    }
    let msd_shift = ((63 - (lo ^ hi).leading_zeros()) / 16) * 16;
    let t1 = Instant::now();
    // pass 1: per-part histogram, local exclusive prefix, local scatter (part-major
    // layout). Afterwards hist[q][d] is the END of bucket d inside part q, so segment d
    // is [hist[q][d-1], hist[q][d]).
    let mut hist: Vec<u32> = Vec::with_capacity(parts * NB);
    let mut pk: Vec<u64> = Vec::with_capacity(n);
    let mut pi: Vec<u32> = Vec::with_capacity(n);
    let (hp, pkp, pip) = (SyncPtr(hist.as_mut_ptr()), SyncPtr(pk.as_mut_ptr()), SyncPtr(pi.as_mut_ptr()));
    pool.run(parts, |q| unsafe {
        let (a, b) = ranges[q];
        let h = hp.get().add(q * NB);
        std::ptr::write_bytes(h, 0, NB);
        for &x in &amt[a..b] {
            *h.add((sortable(x) >> msd_shift) as usize & (NB - 1)) += 1;
        }
        let mut sum = 0u32;
        for d in 0..NB {
            let c = *h.add(d);
            *h.add(d) = sum;
            sum += c;
        }
        for i in a..b {
            let k = sortable(*amt.get_unchecked(i));
            let d = (k >> msd_shift) as usize & (NB - 1);
            let o = a + *h.add(d) as usize;
            *h.add(d) += 1;
            *pkp.get().add(o) = k;
            *pip.get().add(o) = i as u32;
        }
    });
    unsafe {
        hist.set_len(parts * NB);
        pk.set_len(n);
        pi.set_len(n);
    }
    let t2 = Instant::now();
    // bucket totals (parallel over bucket ranges), then global bucket starts
    let mut total: Vec<u32> = Vec::with_capacity(NB);
    let tp = SyncPtr(total.as_mut_ptr());
    let hist_ref = &hist;
    let bucket_ranges = chunk_ranges(NB, threads);
    pool.run(threads, |t| unsafe {
        let (d0, d1) = bucket_ranges[t];
        let out = std::slice::from_raw_parts_mut(tp.get().add(d0), d1 - d0);
        out.fill(0);
        for q in 0..parts {
            let h = &hist_ref[q * NB..(q + 1) * NB];
            let prev = if d0 > 0 { h[d0 - 1] } else { 0 };
            let seg = &h[d0..d1];
            let mut last = prev;
            for (o, &e) in out.iter_mut().zip(seg) {
                *o += e - last;
                last = e;
            }
        }
    });
    unsafe { total.set_len(NB) };
    let mut bstart = vec![0u32; NB + 1];
    for d in 0..NB {
        bstart[d + 1] = bstart[d] + total[d];
    }
    // tasks: contiguous bucket ranges holding ~n / (4 * threads) elements each
    let per = (n + 4 * threads - 1) / (4 * threads);
    let mut cuts = vec![0usize];
    let mut acc = 0usize;
    for d in 0..NB {
        if acc >= per && total[d] > 0 {
            cuts.push(d);
            acc = 0;
        }
        acc += total[d] as usize;
    }
    cuts.push(NB);
    let ntasks = cuts.len() - 1;
    let t3 = Instant::now();
    // pass 2: gather each bucket from the parts into scratch, sort it, emit its indices
    let mut oi: Vec<u32> = Vec::with_capacity(n);
    let oip = SyncPtr(oi.as_mut_ptr());
    let (bstart, total, cuts, pk, pi) = (&bstart, &total, &cuts, &pk, &pi);
    pool.run(ntasks, |t| unsafe {
        let (d0, d1) = (cuts[t], cuts[t + 1]);
        let maxb = (d0..d1).map(|d| total[d] as usize).max().unwrap_or(0);
        let mut ka: Vec<u64> = Vec::with_capacity(maxb);
        let mut ia: Vec<u32> = Vec::with_capacity(maxb);
        let mut kb: Vec<u64> = Vec::with_capacity(maxb);
        let mut ib: Vec<u32> = Vec::with_capacity(maxb);
        for d in d0..d1 {
            let cnt = total[d] as usize;
            if cnt == 0 {
                continue;
            }
            let mut w = 0usize;
            for q in 0..parts {
                let h = &hist_ref[q * NB..(q + 1) * NB];
                let (s0, e0) = (if d > 0 { h[d - 1] as usize } else { 0 }, h[d] as usize);
                if e0 > s0 {
                    let from = ranges[q].0 + s0;
                    std::ptr::copy_nonoverlapping(pk.as_ptr().add(from), ka.as_mut_ptr().add(w), e0 - s0);
                    std::ptr::copy_nonoverlapping(pi.as_ptr().add(from), ia.as_mut_ptr().add(w), e0 - s0);
                    w += e0 - s0;
                }
            }
            let in_b = msd_shift > 0
                && sort_bucket(ka.as_mut_ptr(), ia.as_mut_ptr(), kb.as_mut_ptr(), ib.as_mut_ptr(), cnt, msd_shift);
            let src = if in_b { ib.as_ptr() } else { ia.as_ptr() };
            std::ptr::copy_nonoverlapping(src, oip.get().add(bstart[d] as usize), cnt);
        }
    });
    unsafe { oi.set_len(n) };
    if prof {
        let t4 = Instant::now();
        println!(
            "    sort phases: minmax {:.3}  partition {:.3}  totals+cuts {:.3}  sub-sorts {:.3} ms  ({} tasks, msd_shift {})",
            (t1 - t0).as_secs_f64() * 1e3,
            (t2 - t1).as_secs_f64() * 1e3,
            (t3 - t2).as_secs_f64() * 1e3,
            (t4 - t3).as_secs_f64() * 1e3,
            ntasks,
            msd_shift
        );
    }
    oi
}

neo's side: the call and the contract

the harness, calling the engine · neon-cpp/bench/bench_engine_options.cpp:372
const double s4 = timeIt([&] { sortIndexByDouble(amt.data(), n, perm, &pool); sink = perm[0]; }, 3);
the sort's contract · neon-cpp/core/sort.h:1
// sort.h — stable O(n) sorting of row indices by a double key (parallel radix).
// JS numeric sort semantics: NaN sorts as -Infinity; ties keep input order.

// Fills `idx` with the stable ascending order of keys[0..n). pool may be null.
void sortIndexByDouble(const double* keys, size_t n, std::vector<uint32_t>& idx, Pool* pool);

Every number taken for it

measurementneoRust× neo
time, msBest of three in one process, then the median over seven rounds, every engine run once a round in a shuffled order.1.041.271.21×

Read it with this

  • Taken on a shared machine. Both columns ran in the same shuffled rounds, so the multiple stands, but the times themselves read high.

01.4 · kernel · 1,000,000 rows

sort into a new table

neo 2.88 ms · Rust 4.17 ms · 1.45× neo. Against every engine →

neo

Rust

0 runs

0 runs

What this measures

Sort by amount and build the whole sorted table, every column reordered.

How neo does it

The permutation from the radix sort drives a parallel gather of every column, with the dictionary column moved as ids. The ledger times the gather alone at under three milliseconds for a million rows.

How Rust does it

Every column is gathered through the permutation on the pool, into a fresh arena of bytes and a fresh array of offsets.

sort into a new table · neon-cpp/bench/lang/rust/src/main.rs:1633 · show all 48 lines
/// Tasks are (column, row-chunk) pairs: pass 1 measures bytes per task, pass 2 copies.
fn materialize_mt(t: &Table, perm: &[u32], pool: &Pool, parts: usize) -> Table {
    let n = perm.len();
    let nc = t.cols.len();
    let ranges = chunk_ranges(n, parts);
    let sizes: Vec<usize> = pool.map(nc * parts, |task| {
        let (c, p) = (task / parts, task % parts);
        let (a, b) = ranges[p];
        gathered_bytes(&t.cols[c], perm, a, b)
    });
    let stride = parts + 1;
    let mut bases = vec![0usize; nc * stride];
    for c in 0..nc {
        let mut s = 0usize;
        for p in 0..parts {
            bases[c * stride + p] = s;
            s += sizes[c * parts + p];
        }
        bases[c * stride + parts] = s;
    }
    let mut outs: Vec<(Vec<u32>, Vec<u8>)> =
        (0..nc).map(|c| (Vec::with_capacity(n + 1), Vec::with_capacity(bases[c * stride + parts] + PAD))).collect();
    let ptrs: Vec<(SyncPtr<u32>, SyncPtr<u8>)> =
        outs.iter_mut().map(|(o, a)| (SyncPtr(o.as_mut_ptr()), SyncPtr(a.as_mut_ptr()))).collect();
    pool.run(nc * parts, |task| {
        let (c, p) = (task / parts, task % parts);
        let (a, b) = ranges[p];
        let (op, ap) = ptrs[c];
        let base = bases[c * stride + p];
        let end = bases[c * stride + p + 1];
        unsafe { gather_range(&t.cols[c], perm, a, b, base, end, ap.get(), op.get()) };
    });
    let cols = outs
        .into_iter()
        .enumerate()
        .map(|(c, (mut offs, mut arena))| {
            let total = bases[c * stride + parts];
            unsafe {
                *offs.as_mut_ptr() = 0;
                offs.set_len(n + 1);
                std::ptr::write_bytes(arena.as_mut_ptr().add(total), 0, PAD);
                arena.set_len(total + PAD);
            }
            Column { offs, arena }
        })
        .collect();
    Table { headers: t.headers.clone(), rows: n, cols }
}

neo's side: the call and the contract

the sort's contract · neon-cpp/core/sort.h:1
// sort.h — stable O(n) sorting of row indices by a double key (parallel radix).
// JS numeric sort semantics: NaN sorts as -Infinity; ties keep input order.

// Fills `idx` with the stable ascending order of keys[0..n). pool may be null.
void sortIndexByDouble(const double* keys, size_t n, std::vector<uint32_t>& idx, Pool* pool);

Every number taken for it

measurementneoRust× neo
time, msBest of three in one process, then the median over seven rounds, every engine run once a round in a shuffled order.2.884.171.45×

Read it with this

  • Taken on a shared machine. Both columns ran in the same shuffled rounds, so the multiple stands, but the times themselves read high.

01.5 · kernel · 1,000,000 rows

sum by region

neo 0.020 ms · Rust 0.044 ms · 2.20× neo. Against every engine →

neo

Rust

0 runs

0 runs

What this measures

Total the amount column for each of five regions: a grouped sum, the kernel every dashboard runs.

How neo does it

The region column was dictionary-encoded at load, so its ids are the group numbers and no string is hashed. The sum is taken on the pool in any order only when the column is whole numbers small enough that no addition can round; otherwise it is added in row order on one thread, because a floating-point sum depends on its order, and the contract is the JavaScript loop's result to the bit.

How Rust does it

Each chunk of rows adds into its own small array of group totals on the pool, and the chunks' totals are then added together in a fixed order.

sum by region · neon-cpp/bench/lang/rust/src/main.rs:1713
fn agg_mt(ids: &[u32], amt: &[f64], g: usize, pool: &Pool, parts: usize) -> Vec<f64> {
    let ranges = chunk_ranges(ids.len(), parts);
    let partials: Vec<Vec<f64>> = pool.map(parts, |p| {
        let (a, b) = ranges[p];
        agg_range(&ids[a..b], &amt[a..b], g)
    });
    let mut out = vec![0f64; g];
    for p in &partials {
        for j in 0..g {
            out[j] += p[j];
        }
    }
    out
}

neo's side: the call and the contract

the harness, calling the engine · neon-cpp/bench/bench_engine_options.cpp:454
const double a5 = G <= 16 ? timeIt([&] { groupSumAnyOrder(amtP, idP, n, G, &pool, pairTotal); sink = static_cast<size_t>(pairTotal[0]); }, 9) : 0;
the group sum's contract · neon-cpp/core/groupsum.h:1
// groupsum.h — a typed column's sum, count and extremes per group: what the aggregate node's measures need
// once the column is doubles (toDoubles) and every row has a group number.
//
// The results are the ones a loop over the rows in order gives — `if (isFinite(v)) { sum += v; n++;
// if (v < min) min = v; if (v > max) max = v; }` a group, which is what the JavaScript does — to the bit:
//   • counts and extremes are taken a part of the rows at a time on the pool and the parts joined in row
//     order (a strict comparison keeps the earlier of two equal values, as the loop does);
//   • a sum is added in row order on one thread, because a floating-point sum depends on its order —
//     unless the column is whole numbers small enough that no addition can round (wholeNumbers below),
//     where every order gives the same bits and the rows are summed on the pool, two a step.
// bench/bench_agg_node.cpp times each path against the node and checks it; PHD.md §30.

// The sum alone, any order, two rows a step; for tests and the benchmark (groupStats calls it when it may).
// False, and nothing written, when there are more groups than it is built for.
bool groupSumAnyOrder(const double* x, const uint32_t* id, size_t n, size_t groups, Pool* pool, double* sums);

Every number taken for it

measurementneoRust× neo
time, msBest of three in one process, then the median over seven rounds, every engine run once a round in a shuffled order.0.0200.0442.20×

Read it with this

  • Taken on a shared machine. Both columns ran in the same shuffled rounds, so the multiple stands, but the times themselves read high.

02 · Every number

The same kernels, in other languages

1,000,000 rows · ms, lower is better · 2026-10-12 06:38 · shared machine

kernelneoRust× neo
load (parse + type + dictionary)3.594.601.28×
filter amount > 5000.0170.0382.24×
sort, as a permutation1.041.271.21×
sort into a new table2.884.171.45×
sum by region0.0200.0442.20×

The kernels were ported to Go, Rust, Swift and Zig, each told to beat the C++; what they did better was then taken into the C++. Milliseconds, 1,000,000 rows. Where a port is still ahead, it is shown ahead. These are the million-row figures of the study in the next card, the same record: A round runs every engine once, in an order shuffled each round, and a figure is the median over the rounds (7 at 1,000,000 rows, 5 at 10,000,000 and 3 at 100,000,000). The load is one loop in every binary: three loads first, then three timed whole loads, the previous result still alive during each; its figure is the median over every timed load of every round. Filter, sort and sum are each binary's best of three in a process, and the figure the median of those. Threads: a port is run on 16 and 18 (every core) and its figure for a kernel is the better of the two; neo runs as it ships, on sixteen, and on every core for a load of 256 MB and more. Before a time is taken every engine prints its table as one number, an FNV over every cell, and after it its checks; the line under the table says whether they agreed. What still differs: a port is a benchmark kernel written for this comparison, not a library; each is built as its own run.sh builds it — the Rust and Zig ports for this processor, the Rust port with link-time optimisation, the Swift port with its checks off — and neo at -O3 with none of that; a port builds one dictionary where neo builds three; neo's filter figure is a bitmap where a port's is a list of row numbers; and the file is one synthetic shape (six columns, no field over sixteen bytes).

03 · The code that ran

Rust's side, in full

Rust is a systems language with no garbage collector and a borrow checker in its place, which is why it is the usual answer when someone wants C++ speed without C++. The port runs on every core. The port was written to beat the C++ and given the C++ numbers to beat. Its code is beside each race above, and nothing of it is left out here.

neo's side: the calls and the contracts

neo's kernels are the product, so their bodies stay in the engine. What is published is what a reader needs to judge the comparison: the harness calling the engine, and each kernel's declaration with the guarantees it is held to, down to the order a floating-point sum is taken in. Each contract is beside its race above; the harness lines together, and whatever no race showed, are here. The binaries run on request, and the scripts named below reproduce every number on this page.

the harness, calling the engine · neon-cpp/bench/bench_engine_options.cpp
 194  l.t = csv::parse(raw);
 337  const double f5 = timeIt([&] { Bitmap b = compareDoubles(amt.data(), n, Cmp::Gt, 500, &pool); sink = b.words[0]; }, 7);
 372  const double s4 = timeIt([&] { sortIndexByDouble(amt.data(), n, perm, &pool); sink = perm[0]; }, 3);
 454  const double a5 = G <= 16 ? timeIt([&] { groupSumAnyOrder(amtP, idP, n, G, &pool, pairTotal); sink = static_cast<size_t>(pairTotal[0]); }, 9) : 0;
how energy is read · neon-cpp/bench/energy.h:1
// energy.h — what a process has used, as the operating system's own ledger has it: the energy it was billed,
// its processor time, the wake-ups it caused. The one reader of that ledger, for two questions:
//   what a kernel costs — the Evals page's Energy view (bench_engine_options.cpp reads it around each kernel;
//     tools/energy/energy.cpp checks the counter and reads it for a command it runs;
//     bench/lang/python/yardstick.py reads the same field; PHD.md section 33)
//   what a process costs at rest — the idle studies (scripts/idle_cost.sh and scripts/idle_server.py take
//     `neon_energy --pid <pid>` twice and subtract; PHD.md section 31.1)
//
// macOS on Apple silicon: proc_pid_rusage(RUSAGE_INFO_V6). ri_energy_nj — nanojoules billed to the process's
// threads for the processor cores they ran on, since it started. Not the memory, the disk or the screen, and
// not the machine at rest: what running this code added. (Not ri_billed_energy: against half a second of a
// busy loop that field read 0.08 mJ where ri_energy_nj read 1,887.) Beside it, processor time in nanoseconds
// — `ps` has hundredths of a second, more than a resting window uses in a minute — and the wake-ups. No
// privilege is needed, and any process of the same user can be read, so a tree of processes can be summed.
// Linux: /proc/<pid>/stat and /proc/<pid>/status — clock ticks and context switches. No energy: RAPL is one
// figure for the whole machine and root's to read.
// Elsewhere: nothing is read (ok stays false).
//
// A reading is cumulative; a measurement is the difference of two. The counter moves in steps (a thread's
// share is settled when it leaves a core or enters the kernel), so a window should be a quarter of a second
// or more: `neon_energy --check` prints how far apart the steps are on the machine it runs on.

04 · Diligence

What both sides were held to

Scripts: scripts/scale_study.sh · measured 2026-10-12 · the numbers on this page come from the same ledger as the app's own Evals page, written by neon-cpp/scripts/results_md.py.

More comparisons