Technical investigations

Browser measurements, connection observations, integrity rules and proof contracts. Each article carries its experiment and a hashed reproduction archive.

Browser measurements 7 min read

A CPU quota does not change Chromium 153's processor count

A two-CPU quota left Chromium reporting fourteen processors. Restricting affinity changed the count to two. Nine sessions show why throughput needs its own measurement.

Question

Does a CPU time quota change Chromium 153 reported processor availability in the same way as a CPU affinity restriction?

Reported processors, Chromium 153 with a two-CPU time quota 14
Reported processors, same binary restricted to CPUs 0 and 1 2
2026

Whose round trip did you measure?

A packet experiment separates a terminating proxy’s TCP handshake from the browser’s application response, with a direct-client counterexample.

0.009875 ms Median origin SYN→ACK, relay waits 150 ms each way
306.497 ms Median application echo, relay waits 150 ms each way

Publication standard

About this publication
01

Mechanism

The decisive code, observations or reasoning are in the article body.

02

Counterexample

Claims name their premises and the cases that break them.

03

Conditions

Test conditions and results carry enough detail to inspect.

04

Review

A separate technical review checks the evidence before publication.

The probe runs on your own browser.

The public demo returns the verdict and its named findings.