proxy-benchmark

KO | EN

gitlite — search

#java #chatbot #cloud-native #bash #gpt #rag #ui #tailwindcss #ai #awesome

proxy-benchmark

(★ 9)

Measurement harness for proxy providers, browser engines and scraping targets. Every claim carries the run it came from.

파일 탐색기

ZIP 다운로드

- - bug_report.yml
  - config.yml
  - finding_dispute.yml
  - provider_definition.yml
- - ci.yml
- nodemaven-mark.svg
- - _template.toml
  - custom.toml
  - nodemaven.toml
  - README.md
- - amazon_1000.txt
  - README.md
  - serp_1000.txt
- - availability_20260810T182910Z.jsonl
  - availability_20260810T184646Z.jsonl
  - availability_20260810T190251Z.jsonl
  - availability_20260811T083140Z.jsonl
  - availability_20260811T090035Z.jsonl
  - availability_20260811T094313Z.jsonl
  - availability_20260811T095656Z.jsonl
  - b2b_recon_20260828T105350Z.jsonl
  - b2b_recon_20260828T121114Z.jsonl
  - b2b_recon_20260901T094129Z.jsonl
  - benchmark_20260811T104906Z.jsonl
  - benchmark_20260811T105447Z.jsonl
  - benchmark_20260811T105651Z.jsonl
  - benchmark_20260811T114409Z.jsonl
  - benchmark_20260811T154830Z.jsonl
  - benchmark_20260811T205418Z.jsonl
  - benchmark_20260811T213030Z.jsonl
  - benchmark_20260812T005305Z.jsonl
  - benchmark_20260812T073629Z.jsonl
  - benchmark_20260812T080915Z.jsonl
  - benchmark_20260812T084758Z.jsonl
  - benchmark_20260812T091232Z.jsonl
  - benchmark_20260812T091926Z.jsonl
  - benchmark_20260812T092642Z.jsonl
  - benchmark_20260812T095540Z.jsonl
  - benchmark_20260812T102540Z.jsonl
  - benchmark_20260812T105021Z.jsonl
  - benchmark_20260812T105433Z.jsonl
  - benchmark_20260812T111353Z.jsonl
  - benchmark_20260812T112029Z.jsonl
  - benchmark_20260812T112846Z.jsonl
  - benchmark_20260812T115019Z.jsonl
  - benchmark_20260812T130452Z.jsonl
  - benchmark_20260812T141501Z.jsonl
  - benchmark_20260812T142303Z.jsonl
  - benchmark_20260812T152451Z.jsonl
  - benchmark_20260812T154242Z.jsonl
  - benchmark_20260812T161720Z.jsonl
  - benchmark_20260812T185158Z.jsonl
  - benchmark_20260813T081715Z.jsonl
  - benchmark_20260813T112253Z.jsonl
  - benchmark_20260813T112314Z.jsonl
  - benchmark_20260813T113359Z.jsonl
  - benchmark_20260813T113718Z.jsonl
  - benchmark_20260813T113903Z.jsonl
  - benchmark_20260813T114333Z.jsonl
  - benchmark_20260813T115003Z.jsonl
  - benchmark_20260813T120011Z.jsonl
  - benchmark_20260813T120627Z.jsonl
  - benchmark_20260813T120848Z.jsonl
  - benchmark_20260813T150210Z.jsonl
  - benchmark_20260813T170711Z.jsonl
  - benchmark_20260814T102344Z.jsonl
  - benchmark_20260818T170634Z.jsonl
  - benchmark_20260818T202054Z.jsonl
  - benchmark_20260818T203203Z.jsonl
  - benchmark_20260818T205017Z.jsonl
  - benchmark_20260818T214507Z.jsonl
  - benchmark_20260819T055927Z.jsonl
  - benchmark_20260826T194303Z.jsonl
  - detect_page_20260812T103007Z.jsonl
  - dsl_probe_20260810T154819Z.jsonl
  - dsl_probe_20260810T160708Z.jsonl
  - engine_fingerprint_20260811T135931Z.jsonl
  - engine_fingerprint_20260811T140139Z.jsonl
  - engine_fingerprint_20260811T140158Z.jsonl
  - engine_fingerprint_20260811T143613Z.jsonl
  - engine_fingerprint_20260811T153939Z.jsonl
  - engine_fingerprint_20260812T205618Z.jsonl
  - engine_fingerprint_20260813T103009Z.jsonl
  - engine_fingerprint_20260818T131016Z.jsonl
  - engine_fingerprint_20260818T133832Z.jsonl
  - engine_fingerprint_20260818T133958Z.jsonl
  - engine_fingerprint_20260818T200531Z.jsonl
  - engine_fingerprint_20260818T201319Z.jsonl
  - engine_fingerprint_20260818T202000Z.jsonl
  - engine_fingerprint_20260901T111720Z.jsonl
  - engine_fingerprint_20260901T111855Z.jsonl
  - engine_fingerprint_20260901T114120Z.jsonl
  - gateway_health_20260812T065732Z.jsonl
  - gateway_health_20260812T070823Z.jsonl
  - gateway_health_20260812T070931Z.jsonl
  - gateway_health_20260812T071351Z.jsonl
  - gateway_health_20260812T071828Z.jsonl
  - gateway_health_20260812T072634Z.jsonl
  - gateway_health_20260812T072713Z.jsonl
  - gateway_health_20260812T072937Z.jsonl
  - gateway_health_20260812T073152Z.jsonl
  - gateway_health_20260812T073413Z.jsonl
  - gateway_health_20260812T084122Z.jsonl
  - gateway_health_20260812T084251Z.jsonl
  - gateway_health_20260812T084808Z.jsonl
  - gateway_health_20260812T084834Z.jsonl
  - gateway_health_20260812T084859Z.jsonl
  - gateway_health_20260812T084918Z.jsonl
  - gateway_health_20260812T084919Z.jsonl
  - gateway_health_20260812T084940Z.jsonl
  - gateway_health_20260812T084941Z.jsonl
  - gateway_health_20260812T084942Z.jsonl
  - gateway_health_20260812T085002Z.jsonl
  - gateway_health_20260812T085003Z.jsonl
  - gateway_health_20260812T085910Z.jsonl
  - gateway_health_20260812T085933Z.jsonl
  - gateway_health_20260812T085956Z.jsonl
  - gateway_health_20260812T090041Z.jsonl
  - gateway_health_20260812T090356Z.jsonl
  - gateway_health_20260812T132140Z.jsonl
  - gateway_health_20260813T182233Z.jsonl
  - gateway_health_20260813T200457Z.jsonl
  - gateway_health_20260813T200518Z.jsonl
  - gateway_health_20260813T200520Z.jsonl
  - gateway_health_20260813T200523Z.jsonl
  - gateway_health_20260813T200550Z.jsonl
  - gateway_health_20260813T200618Z.jsonl
  - gateway_health_20260813T200631Z.jsonl
  - gateway_health_20260813T200718Z.jsonl
  - gateway_health_20260818T120052Z.jsonl
  - gateway_health_20260818T122021Z.jsonl
  - gateway_health_20260818T122636Z.jsonl
  - gateway_health_20260818T123750Z.jsonl
  - gateway_health_20260818T123947Z.jsonl
  - gateway_health_20260818T134627Z.jsonl
  - gateway_health_20260818T170506Z.jsonl
  - gateway_health_20260818T170524Z.jsonl
  - gateway_health_20260818T191255Z.jsonl
  - gateway_health_20260818T192809Z.jsonl
  - gateway_health_20260820T083551Z.jsonl
  - geoip_check_20260811T085521Z.jsonl
  - google_429_20260810T175857Z.jsonl
  - google_429_20260810T180915Z.jsonl
  - google_429_20260810T181501Z.jsonl
  - google_429_20260810T181606Z.jsonl
  - google_429_20260811T095556Z.jsonl
  - probehold_20260813T180210Z.jsonl
  - probehold_20260813T180335Z.jsonl
  - probehold_20260813T181311Z.jsonl
  - probehold_20260813T181548Z.jsonl
  - probehold_20260813T181656Z.jsonl
  - probehold_20260813T181820Z.jsonl
  - probehold_20260813T181943Z.jsonl
  - probehold_20260813T182100Z.jsonl
  - probehold_20260813T182356Z.jsonl
  - probehold_20260813T182540Z.jsonl
  - probehold_20260813T182745Z.jsonl
  - probehold_20260813T185138Z.jsonl
  - probehold_20260813T185327Z.jsonl
  - probehold_20260813T201659Z.jsonl
  - probehold_20260813T201805Z.jsonl
  - probehold_20260813T202606Z.jsonl
  - probehold_20260814T052300Z.jsonl
  - probehold_20260814T065213Z.jsonl
  - probehold_20260814T072651Z.jsonl
  - probehold_20260825T231416Z.jsonl
  - probehold_20260825T233230Z.jsonl
  - probehold_20260826T074024Z.jsonl
  - probehold_20260826T074450Z.jsonl
  - probehold_20260826T092819Z.jsonl
  - probehold_20260826T103641Z.jsonl
  - probehold_20260826T105115Z.jsonl
  - probehold_20260826T105407Z.jsonl
  - probehold_20260826T121309Z.jsonl
  - probehold_20260826T121434Z.jsonl
  - probehold_20260826T134902Z.jsonl
  - probehold_20260826T134913Z.jsonl
  - probehold_20260826T142123Z.jsonl
  - probehold_20260826T143724Z.jsonl
  - probehold_20260826T144719Z.jsonl
  - probehold_20260826T151536Z.jsonl
  - probehold_20260826T152533Z.jsonl
  - probehold_20260826T152748Z.jsonl
  - probehold_20260827T141153Z.jsonl
  - probehold_20260827T141355Z.jsonl
  - probehold_20260827T141535Z.jsonl
  - probehold_20260827T142419Z.jsonl
  - probehold_20260827T201123Z.jsonl
  - probehold_20260828T085727Z.jsonl
  - probehold_20260828T213141Z.jsonl
  - probehold_20260831T084544Z.jsonl
  - probehold_20260831T222129Z.jsonl
  - probehold_20260901T102121Z.jsonl
  - probehold_20260901T102123Z.jsonl
  - README.md
  - rtt_gap_20260811T094601Z.jsonl
  - screen_override_20260812T104316Z.jsonl
  - sid_separator_20260820T201312Z.jsonl
  - sid_separator_20260820T202737Z.jsonl
  - surfaces_20260826T205947Z.jsonl
  - surfaces_20260826T210613Z.jsonl
  - surfaces_20260826T210746Z.jsonl
  - surfaces_20260826T210817Z.jsonl
  - surfaces_20260826T211510Z.jsonl
  - surfaces_20260826T220435Z.jsonl
  - surfaces_20260827T070403Z.jsonl
  - surfaces_20260827T070439Z.jsonl
  - surfaces_20260827T070453Z.jsonl
  - surfaces_20260827T191827Z.jsonl
  - surfaces_20260827T192405Z.jsonl
  - surfaces_20260827T192443Z.jsonl
  - surfaces_20260827T192509Z.jsonl
  - surfaces_20260827T195814Z.jsonl
  - tls_echo_20260812T204933Z.jsonl
  - tls_echo_20260812T205035Z.jsonl
  - tls_echo_20260812T205039Z.jsonl
  - tls_echo_20260901T112110Z.jsonl
  - tls_echo_20260901T113512Z.jsonl
  - traffic_20260810T161832Z.jsonl
  - walmart_recon_20260812T140244Z.jsonl
  - walmart_recon_20260812T140955Z.jsonl
- findings_google_429.md
- findings_obscura_tls.md
- quickstart.md
- README.md
- - __init__.py
  - base.py
  - botasaurus.py
  - camoufox.py
  - chromium.py
  - cloak.py
  - curlcffi.py
  - http.py
  - obscura.py
  - rebrowser.py
  - seleniumbase.py
  - zendriver.py
- __init__.py
- __main__.py
- artifacts.py
- blocking.py
- breaker.py
- config.py
- console.py
- gateway.py
- matrix.py
- providers.py
- proxy.py
- queries.py
- relay.py
- sink.py
- stats.py
- targets.py
- - analyze_429.py
  - calibrate.py
  - held.py
  - ladder_three_runs.py
  - peek.py
  - playbook.py
  - report.py
  - results_tables.py
  - ssl_network_split.py
  - ssl_network_split2.py
  - ssl_network_split3.py
  - ssl_network_split4.py
  - ssl_repeat_origin.py
  - ssl_repeat_origin2.py
- - b2b_recon.py
  - capture_sample.py
  - check_geoip.py
  - connect_integrity.py
  - detect_page.py
  - engine_fingerprint.py
  - gateway_health.py
  - geo_align_check.py
  - google_429.py
  - google_surfaces.py
  - obscura_defects.py
  - param_order.py
  - probe_and_hold.py
  - proxy_auth_shape.py
  - rtt_gap.py
  - screen_override.py
  - session_continuity.py
  - sid_separator.py
  - tls_echo.py
  - tls_repro.py
  - vet_warm_pages.py
  - walmart_recon.py
- - build_queries.py
  - redact_runs.py
- benchmark.py
- engine_table.py
- README.md
- run_ladder.py
- conftest.py
- test_artifacts.py
- test_breaker.py
- test_cli.py
- test_connect_integrity.py
- test_engines.py
- test_matrix.py
- test_playbook.py
- test_preflight.py
- test_probe_and_hold.py
- test_providers.py
- test_proxy.py
- test_queries.py
- test_relay.py
- test_report.py
- test_repository.py
- test_runs_are_publishable.py
- test_targets.py
.env.example
.gitattributes
.gitignore
CITATION.cff
CONTRIBUTING.md
LICENSE
Makefile
NOTEBOOK.md
pyproject.toml
README.md
requirements-ci.txt
requirements-dev.txt
requirements.txt
RESULTS.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<a href="https://github.com/nodemaven"><img src="assets/nodemaven-mark.svg" alt="NodeMaven" height="56"></a>

**Find out what is blocking your requests - the proxy, the browser, the host, or
the target itself.**

[![license](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](https://raw.githubusercontent.com/nodemaven/proxy-benchmark/main/LICENSE)

[![python](https://img.shields.io/badge/python-3.11%20%7C%203.13-blue?style=flat-square)](https://raw.githubusercontent.com/nodemaven/proxy-benchmark/main/.github/workflows/ci.yml)
[![rows](https://img.shields.io/badge/rows-16%2C283%20published-blue?style=flat-square)](https://raw.githubusercontent.com/nodemaven/proxy-benchmark/main/data/runs)

</div>

## What this is

A failed request tells you that something failed. It does not tell you what.

The target may be refusing the exit address. It may be reading the browser. The
handshake may be the discriminator. The machine you are running on may be the
variable. Or the proxy may be failing before the request reaches the target at
all.

`proxy-benchmark` separates those and measures them in one time window. It runs
the same targets across controlled combinations of:

- **engines** - plain HTTP clients, stock Chromium, patched browsers, CDP
  drivers and anti-detect frameworks;
- **proxy paths** - gateways, providers, countries, sticky sessions, and a
  direct arm with no proxy at all;
- **browser configuration** - resource blocking, headful, timezone and locale
  alignment, humanized input where the engine has it;
- **hosts** - when the machine itself turns out to be part of the experiment,
  which here it did.

Every attempt is one JSONL row under `data/runs/` carrying the full parameter
set, and the tables below are generated from those rows rather than typed in.

**Bring your own proxy.** No NodeMaven account is needed. A gateway is a `.toml`
file and an engine is a module plus one registry line, so neither ever edits the
runner - point it at [a proxy you already own](#bringing-your-own-proxy).

## Why this exists

The usual debugging loop is: request failed, so the proxy must be bad, so change
the proxy, so it failed again, so the browser must be detected. None of those
steps is justified by a single request.

This asks the question with a control instead:

| Question | The comparison that answers it |
|---|---|
| Is the address the problem? | the same engine through the gateway and direct, in one window |
| Is the browser the problem? | several engines through the same pool, same hour |
| Does the exit country matter? | one engine, `--countries us,any` |
| Does the host matter? | the same configuration on two machines, overlapping hours |
| Does an anti-detect browser actually help? | it and the unmodified control in the same matrix |
| Is the handshake the discriminator? | ClientHello read against the target's answer |
| Does warming an exit help? | the warm-up ladder, all rungs interleaved |

The output that matters is not "this request passed". It is: this variable
changed, these did not, and the outcome moved with it.

## Contents

| | Sections |
|---|---|
| **Start here** | [What this is](#what-this-is) · [Why this exists](#why-this-exists) · [Quickstart](#quickstart) · [Documentation](#documentation) |
| **What is measured** | [What it measures](#what-it-measures) · [How the experiment is structured](#how-the-experiment-is-structured) · [What is under test](#what-is-under-test) · [What the rows carry](#what-the-rows-carry) |
| **What came out** | [Results at a glance](#results-at-a-glance) · [Research findings](#research-findings) |
| **Running it** | [Setup](#setup) · [Running it](#running-it) · [Command reference](#command-reference) · [Operational safety](#operational-safety) |
| **The experiments** | [Front-page entry](#entering-through-the-front-page) · [The warm-up ladder](#the-warm-up-ladder) · [Bringing your own proxy](#bringing-your-own-proxy) · [Adding a provider](#adding-a-provider) · [The axes](#the-axes) |
| **Checking the work** | [Reproduce these numbers](#reproduce-these-numbers) · [Repository layout](#repository-layout) · [Contributing](#contributing) |

All 22 sections are here rather than the popular ones, because the sections a
reader most needs are usually the ones a hand-picked list leaves out. Every
anchor above is checked by `test_every_link_inside_the_repository_resolves`,
which exists because an earlier index in this file spent a day pointing at a
heading that had been deleted.

## Quickstart

A real measurement, no proxy account, no browser download. Measured 2026-08-27 on
a fresh clone: 22 s to install, 31 s to run.

git clone https://github.com/nodemaven/proxy-benchmark && cd proxy-benchmark
    python -m venv .venv
    .venv\Scripts\Activate.ps1                 # macOS, Linux: . .venv/bin/activate
    pip install -r requirements-ci.txt
    python scripts/benchmark.py --engines http --targets ddg_serp \
        --queries 5 --direct --preset none

It prints the plan and what it will cost before it sends anything, then one line
per attempt and a summary:

engine              target        exit                n   pass  verdicts
    http-direct         ddg_serp      direct              5   100%  {'ok': 5}

The first run is deliberately the bare HTTP client with no proxy. There is
nothing to install and nothing to spend, and it establishes that the harness
works before a second variable is introduced.

Every attempt is also a JSONL row under `data/runs/`, which is the only thing
this repository treats as evidence.

From here: the same run [through a proxy](#bringing-your-own-proxy), which needs
no account with anybody; [real browsers](#setup) instead of a bare client; or
[check a number here](#reproduce-these-numbers) rather than take it.

## Documentation

This file is the map. The depth is deliberately split by purpose, so nothing has
to be read before the first run:

| Document | What is in it |
|---|---|
| `README.md` | what the harness does, how the experiment is structured, the headline findings, and every command |
| [`RESULTS.md`](RESULTS.md) | the full tables: denominators, Wilson intervals, Fisher tests, run ids, engine by engine and day by day. Generated from the rows |
| [`NOTEBOOK.md`](NOTEBOOK.md) | how each result was arrived at, what was varied and what was silently held fixed, **and where an earlier conclusion of ours turned out to be wrong** |
| [`docs/quickstart.md`](docs/quickstart.md) | an empty machine to a first measurement, step by step: Python, git, venv, dry-run, browsers, proxies, reading verdicts |
| [`CONTRIBUTING.md`](CONTRIBUTING.md) | adding an engine, a target or a provider, and the rules that are not obvious from the code |

Want the numbers - `RESULTS.md`. Want to know how they were arrived at, including
the ones we got wrong first - `NOTEBOOK.md`. Never used a terminal -
`docs/quickstart.md` assumes nothing; this file assumes you know what a
ClientHello is.

## What it measures

Three layers can reject a request, and debugging fails when you inspect the one
above whichever is actually refusing you. That is the whole reason the axes are
separate.

| Layer | What gives you away | Read with |
|---|---|---|
| IP reputation | datacenter range, a burnt residential exit, a country the target treats harshly | `--countries`, `probe-and-hold`, `gateway-health` |
| Browser signals | `navigator.webdriver`, empty plugin list, a SwiftShader renderer, a `HeadlessChrome` User-Agent | `engine-fingerprint`, `detect-page` |
| TLS handshake | ClientHello shape: cipher and extension counts, absence of GREASE | `tls-echo` |

A different handshake does not by itself explain a different pass rate. Measure
the two together - [here they did not agree](#research-findings).

## How the experiment is structured

A run is a matrix, and every axis is independent: target, engine, provider,
country, gateway parameters, resource blocking, headful, geo alignment, entry
shape, warm-up rung. They do not nest inside one another, and that is the point -
any one can be varied while the rest are held, and all of them are on every row.

Two properties do most of the work:

- **Cells interleave at batch granularity, never run in sequence.** Finishing one
  engine before starting the next would measure the afternoon as well. The hour
  is the largest confound this repository has found: the same gateway, country
  and browser moved 69 points to 52 between two windows of one afternoon.
- **A matrix that could not be controlled is refused, not quietly adjusted.** If
  an option applies to some engines and not others, the run would compare a
  humanized Camoufox against an unhumanized everything else and read it as an
  engine difference. Every engine declares what it supports and `--dry-run`
  refuses the matrix before it starts.

## What is under test

11 frameworks, one registry line each. Anything missing from the machine reports itself unavailable and names the install command, and the rest of the matrix still runs - `--dry-run` prints that list.

| `--engines` | what it is | needs |
|---|---|---|
| `http` | Plain HTTP client. No browser, no JavaScript. The cheap baseline | nothing beyond `requests` |
| `chromium` | Stock Playwright Chromium. The unmodified control every other engine is measured against | `playwright install chromium` |
| `camoufox` | Camoufox: a patched Firefox driven through Playwright | `camoufox fetch` |
| `patchright` | Patchright: Playwright with the automation tells patched out | `patchright install chromium` |
| `obscura` | Obscura: a from-scratch browser in Rust, driven over CDP | a built Obscura binary |
| `cloak` | CloakBrowser: a patched Chromium that hands back a Playwright browser | `cloakbrowser.ensure_binary()` |
| `curlcffi` | A scriptless client wearing Chrome's handshake. The control for the control | `curl_cffi`, no browser |
| `seleniumbase` | SeleniumBase UC mode: the WebDriver family, which the matrix did not have | the host's installed Chrome |
| `zendriver` | Zendriver: Chrome over raw CDP, with no WebDriver and no Playwright | the host's installed Chrome |
| `rebrowser` | Rebrowser: Playwright with the `Runtime.enable` leak patched out | `rebrowser_playwright install chromium` |
| `botasaurus` | Botasaurus: the host's Chrome over raw CDP, driven by a scraping framework | the host's installed Chrome |

Any of them takes a `:direct` suffix, which runs that engine around the gateway inside the same matrix, so the proxy and the no-proxy arm are measured in one window rather than an hour apart.

Six targets, chosen because they fail differently rather than because they are
popular: `google_serp`, `bing_serp`, `ddg_serp`, `amazon_search`,
`walmart_search`, and `ipinfo` - which is not a target but an echo service, used
to prove the path works before anything is concluded from a refusal.

## What the rows carry

Every attempt writes one JSONL row: engine and engine version, target, provider
and gateway parameters, country, preset, headful, geo, entry shape, warm-up rung,
session and query, the verdict and the marker counts behind it, the failure
reason, timing, and bytes. `ROW_FIELDS` in `nmbench/engines/base.py` is the
schema. Those files are the source of truth, and the tables in this README and in
`RESULTS.md` are generated from them - a number nobody has to remember to update
is a number that cannot drift.

**Verdicts come from page content, not HTTP status.** The same Google reCAPTCHA
page arrived once as 429 and once as 200, so a run judged by status
scores the second as a success. There is no boolean `success` column:

| verdict | what it means |
|---|---|
| `ok` | the target returned the page that was asked for |
| `captcha` | a challenge stood in front of the result |
| `consent` | a consent or cookie wall stood in front of the result |
| `block` | the target refused explicitly |
| `empty` | a body arrived and the result was not in it |
| `error` | the attempt never completed - the harness, never the target |

The last two are the ones that decide whether a benchmark measures anything:

- **`empty` is not `block`.** Google hands a scriptless client a 92 KB "enable
  JavaScript" scaffold that stays on `/search` and rejects nothing, so scoring it
  as a block credits Google with a refusal it never made. 14 of 14 such rows
  carried `enablejs` and none carried `recaptcha`.
- **`error` is ours.** A timed-out selector, a browser that would not launch and
  a query that never reached the box produced no evidence, so they produce no
  verdict. A harness that counts its own crashes as target refusals can
  manufacture a very convincing result while measuring almost nothing.

Four more columns are easy to misread:

- **A refused address diverts the request, and the status does not say so.**
  Google answers a refusal by sending the request to `/sorry/`, with a 200 about
  a quarter of the time. `report.was_served` - a 200 whose final URL keeps the
  host and path asked for - is the test, and it is a property of the exchange, so
  nothing has to know a target's name.
- **A batch is one session, and a session is the unit.** Ten queries through one
  browser is one identity doing ten searches; ten browsers doing one query each
  is a different experiment. The claim has been false once - until 2026-08-11
  Camoufox opened a fresh context per query and discarded its cookie jar while
  every other engine carried one - and `session-continuity` is the offline probe
  that caught it.
- **`bytes` is two measurements and `relayed` says which.** Playwright engines
  count through `page.route` and see page resources; the relay counts sockets and
  sees request headers and TLS overhead as well. Never pool them. The relay figure
  is what a provider bills, and it adds a loopback hop, so `elapsed_ms` is not
  comparable across `relayed`.
- **The matrix carries an unmodified control.** `chromium` is Playwright's
  Chromium with no arguments, no user agent override and no patches;
  `navigator.webdriver` is `true` and stays that way, because without it a pass
  rate cannot be told apart from the target letting everything through.
  `tests/test_engines.py` reads the source of `ChromiumEngine.open` and fails if
  `args=` or `user_agent` appear.

**Response bodies are kept, gzipped.** A verdict is one word about 92 KB of
markup, and the question that decides a report is usually asked after the run.
Non-`ok` bodies plus a sample of the passes, controlled by `--no-bodies` and
`--sample-ok`. The archive is gitignored, unlike `data/runs/`, because exit
addresses appear in embedded links. Re-reading 250 stored Amazon bodies offline
found an Akamai interstitial and an AWS WAF challenge filed as refusals, and moved
21 historical rows at no traffic cost.

## Results at a glance

Best and worst engine per target, from the 10432 attempt rows in `data/runs/benchmark_*.jsonl`. `pass` is `ok` over judged attempts - harness and path failures are counted separately and excluded from the denominator, because an engine that crashes is not an engine the target refused.

| target | best | worst | rows |
|---|---|---|---|
| `amazon_search` | `chromium/none` 96% (419/436) | `patchright/none` 63% (288/457) | 3816 |
| `google_serp` | every engine below 5%, best is 1.1% (5/460) - **not an engine comparison - the whole column is one browser on one host that this target refuses** | - | 3811 |
| `bing_serp` | `chromium/light` 100% (45/45) | `http-direct` 76% (34/45) | 372 |
| `ddg_serp` | `camoufox/light` 100% (44/44) | `chromium-direct/light` 22% (10/45) | 339 |
| `walmart_search` | no cell reaches 30 judged attempts, so no engine is named | - | 35 |

On the one target with enough evidence to rank engines, the top of the table is a **tie and not a podium**: `chromium`, `rebrowser`, `botasaurus`, `camoufox`, `zendriver`, `seleniumbase` sit within 4 points of each other and a two-sided Fisher exact, corrected for the 7 comparisons made, separates none of them. The first of them is `chromium`, which is the unmodified control.

Amazon and the two smaller search engines are a win. **The Google row is not an engine comparison and must not be quoted as one.** Every cell of it was taken on one Linux VPS. Run again with the same engine through the same gateway, a Windows workstation was served 39% (24/61) against 0% (0/84) from the VPS, two-sided Fisher p = 3.7e-11; cut to the one window where both machines were running at once it is 36% (8/22) against 0% (0/10), p = 0.035. The floor is real, it belongs to that client, and it is not a property of the proxies.

**[Full tables -> RESULTS.md](RESULTS.md)** - the 130-hour run (`benchmark_20260819T055927Z`, 2026-08-19 06:00 to 2026-08-24 16:12 UTC) engine by engine, Google day by day, and everything measured before it, split by host and by path.

**Three row counts appear on this page and they count different things.** The
badge counts every line in the committed `data/runs/*.jsonl` - matrix runs,
probe-and-hold windows, fingerprints, gateway checks. The table above counts only
matrix attempts that carried a query, which is `benchmark_*.jsonl` minus the
plan and summary lines. The `rows` column is per target within that. Each is
generated from the files and a test fails when the badge and the files disagree.

## Research findings

Everything below was measured with this harness between 10 August and 1 September
2026, and none of it is a standing fact about the internet: a target's defences
move, so a rate measured in that window is evidence about that window. The dates
sit here once rather than on each line, because a reader deciding whether to
trust one of these needs the run id and the denominator, and those live in the
section each line links to along with the date it stopped being true.

- **Chrome spends 43 MB per fresh profile talking to Google before you ask it
  for anything.** 43.2 MB of a 43.4 MB idle window on
  `optimizationguide-pa.googleapis.com`, on a browser parked on `about:blank`.
  At one profile per attempt that is about 43 GB per thousand attempts, billed
  as residential traffic, for a file no target ever sees.
  [How it was counted](NOTEBOOK.md#chrome-pays-its-vendor-43-mb-per-profile-and-the-pool-was-billed-for-it)
- **On Amazon the unmodified browser finished in the leading group.** Stock
  Chromium 96% (419/436) against 63% (288/457) for the lowest anti-detect
  engine, over 3530 judged Amazon attempts in one 7630-row run. Six engines sit
  within four points at the top and no test separates them, so the top of that
  table is a tie rather than a ranking - and the control is inside it.
  [Full table](RESULTS.md#amazon_search-in-the-130-hour-run)
- **The same code, gateway and target scored 39% on one machine and 0% on
  another.** 24/61 from a Windows workstation against 0/84 from a Linux VPS in
  overlapping hours, Fisher p = 3.7e-11. The client machine is a variable a
  proxy comparison usually holds fixed without saying so.
  [The split](RESULTS.md#the-host-separated-from-the-date)
- **On DuckDuckGo one substring in the User-Agent accounted for the whole
  split.** 95 of 95 pass for engines whose UA omits `HeadlessChrome`, 0 of 50
  for the two that carry it, across three browser families and two drivers.
  Nothing else varied moved it, so a headless Chromium measured there is
  reporting its own UA rather than its exit.
  [The split](NOTEBOOK.md#duckduckgo-is-reading-the-user-agent-and-the-split-is-total)
- **On Google the exit address dominated everything else we varied.** Given a
  served page, pass was 83 of 83 and did not vary by country, while the chance
  of being served ran from 13% to 62% depending on the exit. The browser did not
  separate the cells, and no absolute rate here should be read as current.
  [The decomposition](NOTEBOOK.md#exit-yield-is-a-country-axis-and-us-is-the-worst-of-them)
- **The TLS handshake explains neither Google nor Amazon.** Chromium, Patchright
  and Obscura emit a byte-identical ClientHello and their pass rates differ by
  44 points. If you do compare, compare JA4 - Chrome shuffles extension order
  per connection, so a JA3 difference between two Chromium engines is noise.
  [What was read](NOTEBOOK.md#the-handshake-was-read-and-it-is-not-the-discriminator)
- **Timezone and locale alignment did not pay off in either arm we ran.** Flat
  on Patchright (34% against 35%), and zendriver lost six sevenths of its yield,
  57% down to 9%, p = 0.0008. Two engines is a thin basis for a rule, but
  nothing measured here argues for switching it on.
  [Both arms](NOTEBOOK.md#the-axes-and-the-capabilities-that-are-refused-rather-than-dropped)
- **Our own harness was getting the pool banned.** One unauthenticated CONNECT
  per session, sent by the browser before anything else, was tripping an IP ban
  that looked like a gateway floor for days.
  [How it was found](NOTEBOOK.md#the-floor-was-an-ip-ban-and-this-harness-was-tripping-it-itself)
- **One page of warm-up moved nothing in our window.** 32% against 30%,
  intervals almost coincident. This refutes nobody: the protocol came to us from
  an operator, and the 75% that travels with it was mentioned in conversation as
  a figure once reached - not as a before-and-after pair, and with no
  denominator behind it. What our arm rules out is one page, which is what the
  ladder now goes past.
  [The ladder](#the-warm-up-ladder)
- **Six pages of warm-up moved a great deal.** Four rungs interleaved in one
  run, because the hour is the largest confound here: **11%, 19%, 33% and 82%**
  at warm depths 0, 2, 4 and 7, over 35, 48, 33 and 33 judged attempts. Cold
  against deepest is z = 5.82. It is one run on one host, Chrome 151.0.7922.34
  headful through Patchright, and it does not yet say what the depth is doing -
  four of the six pages are Google's own, so "Google's infrastructure was told
  about this exit" and "the browser lived through six navigations" both fit
  every row of it. A neutral rung at the same depth is what separates them, and
  it is the next run rather than a conclusion here.
  `data/runs/probehold_20260831T222129Z.jsonl`

Nothing here is a NodeMaven sales number. Where the pool loses, the run file
saying so is in `data/runs/` with everything else.

**Five of these ten replaced an earlier claim of ours, and both versions are
still in the notebook** - Amazon, the warm-up, the Google levels, the idle
traffic and the ban. The Amazon one reversed outright: on a workstation in early
August, Camoufox was served 90% while every Chromium engine met the throttle,
which read as a Firefox-against-Chromium result. On the server the unmodified
control came out on top and the Firefox reading was gone. A number here is a
reading of the hours it was taken in, and the ones that changed are labelled
rather than quietly edited.

## Setup

Python 3.11 or newer, run from a checkout. There is no `[project]` section to
install, because the committed query lists and `data/` are part of the instrument.

python -m venv .venv
    .venv\Scripts\Activate.ps1          # macOS, Linux: . .venv/bin/activate
    pip install -r requirements-dev.txt
    python -m playwright install chromium
    python -m patchright install chromium
    python -m rebrowser_playwright install chromium
    python -c "import cloakbrowser; cloakbrowser.ensure_binary()"
    camoufox fetch
    copy .env.example .env               # macOS, Linux: cp .env.example .env

Playwright, Patchright, rebrowser and cloakbrowser pin four different Chromium
builds and **no two share a download**, so a fresh machine fetches four browsers -
the build is what several findings here are about. `zendriver`, `seleniumbase` and
`botasaurus` download nothing and drive the host's installed Chrome, so a machine
without Chrome loses three engines and the rest carry a build nobody pins.

None of it is mandatory. An engine whose dependency is missing reports itself
unavailable and names the install command; the rest of the matrix runs.
`--dry-run` prints that list, so run it first on a new machine.

**Headful on a headless host needs `xvfb-run -a`.** `--headful` is the difference
between `Chrome/...` and `HeadlessChrome/...` on the wire, which is the whole of
the DuckDuckGo finding. A virtual display does not restore the GPU, so WebGL falls
back to software and a headful server run is not a headful workstation run.

Obscura is not on PyPI. Download the **`-stealth`** archive, unpack it, put the
directory on PATH. The plain archive is a different build and the stealth patches
are the thing being measured.

`.env` holds `NODEMAVEN_LOGIN`, `NODEMAVEN_PASSWORD`, `NODEMAVEN_HOST` and
`NODEMAVEN_PORT`. **The prefix is the provider id**, so `oxylabs.toml` reads
`OXYLABS_LOGIN` and two accounts sit in one `.env` - which is what a matrix
interleaving two providers needs. `.env` is gitignored, `config.py` is the only
reader, and it resolves on first use so everything else imports and tests on a
machine with no account.

Before spending anything:

make check                        # ruff plus the offline suite
    python scripts/benchmark.py --dry-run

The suite is offline. A green suite is the precondition for spending traffic.

## Running it

`python -m nmbench` lists every command, what it answers, and which ones spend
traffic. It is a dispatcher: the remaining flags go to the script untouched, and
every script still runs directly by path.

python -m nmbench                            # what exists, and what it costs
    python -m nmbench benchmark --dry-run
    python -m nmbench engine-fingerprint         # offline, sends nothing

A first matrix, one engine against the unmodified control:

python scripts/benchmark.py --engines patchright,chromium \
        --targets google_serp --queries 40 --batch 10 --headful

The `:direct` suffix puts the same browser on both sides of the gateway inside one
window; two runs an hour apart would measure the hour as well. A global `--direct`
forces every cell direct and cannot be partly undone by a spec that omitted the
suffix.

python scripts/benchmark.py --engines chromium,chromium:direct,camoufox \
        --targets amazon_search --queries 100 --batch 10

Resume skips attempts already judged, so an interrupted run does not re-ask the
targets:

python scripts/benchmark.py --resume data/runs/benchmark_<stamp>.jsonl

Then read what it said, and what it really cost:

python scripts/analysis/report.py
    python scripts/analysis/calibrate.py

### Entering through the front page

Arriving at `/search?q=` is one request carrying a query string, with no keystroke
behind it, no referrer and no form submission - a shape no person produces. It is
now an axis: `entry` is on every row, `url` for that shape and `home` for landing
on the front page and typing into the box.

python scripts/probes/probe_and_hold.py --engines patchright,zendriver \
        --identities 20 --series 3

The protocol is an operator's: one sticky exit per session, type on the front
page, drop the address if the probe is refused, hold it for a series if the probe
is served. Read the result with `scripts/analysis/held.py`.

### The warm-up ladder

The operator's protocol above includes opening a page or two on the target before
asking it anything, and a figure of 75% travels with it. Measured here, one page
moved 32% to 30%.

Be careful what that is being compared against, because this document was not for
two days. The 75% reached us in conversation, as a number an operator had once
seen on their own pool, country mix and hour. It was never stated as a
before-and-after pair, so there is no 20%-to-75% effect to fail to replicate and
no claim of anyone's to refute. What this arm has is its own denominator, and
that is all it has.

That result has two readings and one arm cannot tell them apart: either warming
does nothing, or **one page is not warming**. `--warm` is a ladder rather than a
switch so the second reading gets a denominator.

| rung | what it opens | what a gap to the rung below isolates |
|---|---|---|
| `L0` | nothing. The exit meets the target for the first time at the probe | the baseline every row taken before 2026-08-26 was measured at |
| `L1` | one page of the target's own | whether being seen once before the query is worth anything |
| `L2` | several of the target's surfaces, on more than one host | one visit against several. Separates "seen at all" from "seen more than once" |
| `L3` | `L2`, preceded by third-party pages | whether an exit is better off arriving from somewhere else. The third-party pages carry the target's own analytics and ad tags, so the exit is reported to its infrastructure without a navigation to it |
| `N1` | one third-party page, not the target's | against `L1`: whether one visit has to be the target's own to be worth anything |
| `N3` | six third-party pages | against `L3`: whether the 82% is the depth or the four Google surfaces inside it |

`N1` and `N3` are controls on **composition**, not steps in depth. Each matches
the delivered page count of the chain rung it answers and shares none of that
rung's target-owned pages, which is why they are excluded from the cumulativeness
rule below - being a superset of the rung they control is the one thing they must
not be. Neither is a Google-free arm and the output should not be read as one:
`entry=home` navigates to the front page before it can type, so every arm
contacts the target immediately before the probe.

Three things make the gaps readable rather than decorative:

- **The rungs are cumulative and each ends on the same page.** `L3` is a strict
  superset of `L2`, which is a strict superset of `L1`, and all three finish on
  the page `L1` visits before the front page. So whatever `L1` buys is held while
  the rungs above it vary, `warm_depth` is an ordering, and a difference between
  two rungs is a difference in **what was added** rather than in two unrelated
  sequences. A test enforces this rather than a comment asking for it.
- **All rungs interleave in one process.** The hour is the largest confound this
  repository has: the same gateway, country and browser moved 69 points to 52
  between two windows of one afternoon, and the same target went
  39% on one host and 0% on another in overlapping hours. Rungs run one after
  another would price the hour and call it depth.
- **The pages belong to the target, not to the probe.** A probe that knew a
  domain would be a probe that could warm one target better than another. A rung
  a target has not declared is refused rather than answered with a shorter one,
  because a row labelled `L3` whose warm-up was `L1`'s is a wrong result and not
  an error - it looks exactly like the deeper warm-up not helping. `amazon_search`
  declares `L1` only: the rungs above it were designed against Google's refusal
  and nothing here says they transfer.

python scripts/probes/probe_and_hold.py --targets google_serp \
        --warm off,L1,L2,L3 --identities 24 --series 5 --dwell 20,45

For a run nobody is going to watch, `scripts/run_ladder.py` wraps that one
command. It does not change the shape of the experiment - the rungs still
interleave inside a single process, because a supervisor that ran them in turn
would reintroduce the confound the interleaving exists to remove. What it adds
is a preflight that refuses a bad plan or a dead pool in seconds rather than at
hour three, a log per attempt under `data/logs/`, and a restart rule that is
deliberately narrow: an attempt is retried only if it died within ten minutes,
because a run that fell over on startup has lost nothing while one that fell
over at hour two is worth more than a second attempt at a different hour. Two
attempts are two run files, and the summary says not to pool them.

It also defaults to `--engines patchright` rather than to the registry default,
for a reason that is a measurement: through the pool at
`google_serp`, patchright answered 96 ok of 223 while botasaurus managed 1 of
87, seleniumbase 0 of 86 and camoufox 0 of 33. A ladder on an engine that cannot
reach the target compares four zeroes.

python scripts/run_ladder.py --identities 12

**What this run cannot do, stated before it is run.** At 24 identities per rung,
a move from 39% to 60% is Fisher p ~ 0.25 - not a result. The ladder is a sieve
on **direction**: it says which rung is worth 90 identities, and the confirming
run is a separate one. Quoting a rung ordering off 24 apiece would be the same
error as the four discordant pairs at p = 0.125 elsewhere in this repository.

Cost is dwell, and it is most of the run: at `--dwell 20,45` the three warm rungs
average 65, 130 and 195 seconds per identity, so 24 identities is about 2.6 hours
of dwell before a single probe, hold or gap is counted.

**What the ladder does not reach.** Every rung is a sequence of navigations -
`visit()` is one `goto`, which is the one method every engine's page object has,
which is why warming needs no engine support. Clicking a link, clicking a result
and refining a query are a different shape of session and none of them is here.
If the ladder comes back flat, that is the next thing to build rather than a
conclusion that history does not matter.

### Bringing your own proxy

Any proxy works - bought from anyone, or running on a box you own - and no account
with anybody is needed. Four values in `.env`:

CUSTOM_HOST=1.2.3.4
    CUSTOM_PORT=8000
    CUSTOM_LOGIN=your_login
    CUSTOM_PASSWORD=your_password

Check it before spending anything on it. Ten CONNECTs, a few hundred bytes,
nothing sent to any target. It is the only check that separates a wrong password
from an unreachable host, because the gateway answers both with a status that
names neither:

python -m nmbench gateway-health --provider custom

Then run whatever you like through it:

python scripts/benchmark.py --providers custom \
        --engines http --targets bing_serp --queries 20 --preset none

`data/providers/custom.toml` is already written for the shape most proxies have:
one endpoint, a login, a password, no settings encoded in the username. Nothing to
transcribe, no code.

A gateway with no session parameter cannot be asked for a different exit, so every
attempt leaves from one address. The runner prints this on the plan line:

| Still answerable | Closed |
|---|---|
| which browser gets past which target, what a target costs in bytes, whether your setup announces itself | exit yield, how many queries burn an address, whether rotation helps |

If your provider does sell countries or sticky sessions inside the username, copy
`_template.toml` and write the dialect down there instead.

### Adding a provider

A provider is a username format: gateways take country, sticky session and quality
filter inside the proxy username, and every vendor picks its own separators and
names. So it is a file rather than a module - data cannot branch, and
`tests/test_repository.py` reads the runner's source and fails if it ever compares
against a provider name.

cp data/providers/_template.toml data/providers/oxylabs.toml
    # fill in the dialect, then set OXYLABS_LOGIN and OXYLABS_PASSWORD in .env
    python scripts/benchmark.py --providers nodemaven,oxylabs \
        --engines patchright --targets google_serp --queries 40 --batch 1

`--providers` is an axis like every other one: cells interleave at batch
granularity, because provider A at 10:00 against provider B at 14:00 measures the
afternoon. The cell key names the provider only when the axis is varied, so runs
recorded before the axis existed still match `--resume`.

**Every definition declares its provenance, and it is the first field to read.**
`status = "measured"` means rows in `data/runs/` came through that gateway;
`status = "documented"` means the dialect was transcribed from the vendor's
documentation and never sent a byte. `--dry-run` prints it.

That is load-bearing because **a wrong username is invisible**. The gateway
measured here answers an unrecognised parameter name with HTTP 200 and the setting
silently dropped, so the run completes and every row claims a setting that was
never applied. A name outside `known_params` is refused before a request exists,
and `--param` is validated against every provider in the matrix before the first
cell opens.

Only `nodemaven.toml` ships, and it is the only gateway any number here was
measured through.

### The axes

An option only some engines implement is the failure this harness is built
against: the run would compare a humanized Camoufox against an unhumanized
everything else, and that reads as an engine difference. Every engine declares
what it supports and the runner refuses a mixed matrix outright.

| Flag | Declared by | Engines that have it |
|---|---|---|
| `--preset` | `supports_blocking` | the Playwright-driven ones plus obscura - `page.route` is a Playwright API and obscura has its own |
| `--headful` | `supports_headful` | everything with a window, so everything except the two scriptless clients and obscura, whose `serve` has no such flag |
| `--geo align` | `supports_geo_align` | camoufox, patchright, rebrowser, cloak, zendriver, botasaurus |
| `--humanize` | `supports_humanize` | camoufox, cloak |
| typed entry | `supports_typing` | camoufox, chromium, patchright, rebrowser, cloak, zendriver |

The table is a summary and the code is the authority: `--dry-run` refuses a matrix
before it starts, rather than leaving a reader to check a list that has rotted.

**A mixed matrix needs `--preset none`.** The default is `light`, and blocking for
some columns and not others measured 4 KB against 9.9 MB on the same Google
refusal page - a 2000x engine difference produced entirely by the
flag. It moves verdicts too: a page that never loads its script is judged on
markup that was never finished.

**`--countries` needs no engine feature**, because the host country is the
alignment - the browser reports this machine's timezone and language list whatever
address it leaves from:

python scripts/benchmark.py --engines camoufox,chromium,chromium:direct \
        --countries ru,us --targets bing_serp --queries 20 --preset none

A direct cell has no country, so the axis collapses for it and it is built once.

**`--geo align`** hands the browser the exit's own timezone through the browser's
emulation rather than by patching a JavaScript property, which reads back
unpatched from an iframe and from a Web Worker. The unmodified control stays at
`False`: the axis is read within one engine, aligned against unaligned, in one
window. Whichever was used is on every row.

**Each target draws from its own committed query list.** A shop and a search
engine have to run in one window and cannot take the same strings: asked
"photosynthesis exam questions", Amazon answers with an empty shelf, which is
indistinguishable from a soft refusal once it is a verdict. `--query-list` forces
one list on everything when that is the question.

## Command reference

Everything above on one page, for reading rather than for learning from. The code
is the authority: `python -m nmbench` lists every command and marks the ones that
send nothing, and `-h` prints the flags with the reasoning attached.

**Start here, by what you are trying to do.**

| I want to | Command | Spends |
|---|---|---|
| See what exists and what each thing costs | `python -m nmbench` | nothing |
| Check the tree is sane before anything else | `make check` | nothing |
| Know what a run would cost before running it | `python scripts/benchmark.py --dry-run` | nothing |
| Know which engines can run on this machine | `--dry-run` again - it prints the ones that cannot and why | nothing |
| See what each browser tells a page about itself | `python -m nmbench engine-fingerprint` | nothing |
| Check a gateway is alive and my username is right | `python -m nmbench gateway-health` | a few hundred bytes |
| Compare two engines on one target | `--engines patchright,chromium --targets google_serp` | traffic |
| Ask what the gateway itself contributes | `--engines chromium,chromium:direct` - the same browser on both sides, one window | traffic |
| Compare countries | `--countries us,any` | traffic |
| Compare two providers | `--providers nodemaven,custom` | traffic |
| Enter through the front page instead of a query URL | `python -m nmbench probe-and-hold` | traffic |
| Continue a run that was interrupted | `--resume` , or `--resume <path>` | traffic |
| Read what a run said | `python scripts/analysis/report.py` | nothing |
| Read one run line by line | `python scripts/analysis/peek.py <file>` | nothing |
| Find out what a run really cost, for the next estimate | `python scripts/analysis/calibrate.py` | nothing |

**Every flag of the matrix runner.** Defaults are what you get for saying nothing,
and two of them are worth knowing before a first run.

| Flag | Values | Default | What it changes |
|---|---|---|---|
| `--engines` | any of `http`, `curlcffi`, `chromium`, `patchright`, `rebrowser`, `cloak`, `camoufox`, `obscura`, `seleniumbase`, `zendriver`, `botasaurus`, comma separated, each optionally with `:direct` | `camoufox` | the frameworks under test. `:direct` runs that one around the gateway in the same matrix |
| `--targets` | `google_serp`, `bing_serp`, `ddg_serp`, `amazon_search`, `walmart_search`, `ipinfo` | `google_serp,bing_serp,ddg_serp` | who is asked. `ipinfo` is the cheap one: it answers with your exit address and judges nothing |
| `--queries` | a number, or `all` | `30` | how many strings are drawn from the target's list |
| `--query-list` | `serp_1000`, `amazon_1000`, `smoke` | each target's own | forces one list on the whole matrix. Only when that is the question - a shop asked a physics question answers with an empty shelf |
| `--batch` | a number | `10` | queries per browser. **This is the session**, and it is the unit every number describes |
| `--countries` | comma separated, `any` allowed | `us` | an axis. See the warning below |
| `--providers` | ids of files in `data/providers/` | `nodemaven` | an axis, interleaved at batch granularity |
| `--preset` | `none`, `light`, `aggressive` | `light` | resource blocking. **A mixed matrix needs `none`** and the runner refuses it otherwise |
| `--geo` | `off`, `align` | `off` | hands the browser the exit's own timezone. Measured: buys nothing and costs zendriver most of its yield |
| `--headful` | flag | off | a real window. Changes `HeadlessChrome` to `Chrome` in the User-Agent, which is the whole of one target's answer |
| `--humanize` | flag | off | humanized cursor, where the engine has it. Refused for a matrix holding one that does not |
| `--direct` | flag | off | no proxy at all. A control, not a normal mode |
| `--channel` | e.g. `chrome` | bundled build | which Chromium build. It reaches the cell key, so two builds stay separable |
| `--param` | `KEY=VALUE`, repeatable | none | an extra gateway parameter. Every recognised one joins the sticky session key, so adding one moves you to a different exit |
| `--breaker` | a number | `10` | consecutive failures that stop a cell. A pool-safety setting, not a patience one |
| `--pause` | seconds | `5.0` | between attempts. This is a shared production pool |
| `--resume` | nothing, or a path | off | skips attempts already judged in that file, or in the newest run |
| `--dry-run` | flag | off | prints the plan and the cost, sends nothing |
| `--no-bodies` | flag | off | stops keeping response bodies, and gives up re-judging this run offline forever |
| `--sample-ok` | a number | `2` | passing bodies kept per engine and target. Failures are always kept in full |

**`--countries` defaults to `us`, and `us` is the worst setting measured** - 13%
of US exits served against 58% on `any`. A first run on the defaults looks worse
than this pool actually is. The default is not a recommendation: country is part
of the cell key, so changing it would stop all 44 committed benchmark files from
matching `--resume`. Pass `--countries any`, or both if the country is the
question - `us` and `any` in one window is what turns the gap into a finding
rather than into a flattering number.

**`--batch` is the other one.** `--batch 1` opens a fresh browser per query, so
every attempt is a new identity on a new exit; `--batch 10` is one identity doing
ten searches. Different experiments, different questions, both recorded on every
row. At `--batch 1` a Chrome-driving engine also pays a fresh profile's 43 MB
vendor fetch on every attempt.

## Operational safety

This harness sends real traffic to real targets through a shared production pool.
More requests do not make a better experiment, and past a point they stop making
an experiment at all - once a target is reacting to the harness, what is being
measured is the harness.

**The circuit breaker is not an error handler.** N consecutive failures stop a
cell and it stays stopped: every retry after a refusal confirms automation to the
target and degrades the exit ranges for every other customer on the account. There
is no "error, new sid, retry" path here.

N is measured. Over 129 cells and 1464 attempts, the chance an attempt succeeds
given the failures before it in its own cell is 75% at zero, 5.8% at five and 1.6%
from the sixth onward. Stopping at 5 records a partial refusal as a total one;
running past 10 spends about 98 retries per delivered page. `--breaker` defaults
to 10, and `CircuitBreaker` stays at 5 because every `google_429` run on disk was
measured there.

**Pause between requests.** 3-5 seconds minimum.

**Never print or paste `Proxy-Authorization`.** It is base64, not encryption.

**`data/runs/` is committed, and masked.** Exit addresses are reduced to their /24
and the proxy username to `<login>` - those are real people's home connections, and
the username identifies the account. Masking happens at the one choke point every
row passes through, and `tests/test_runs_are_publishable.py` fails if a full
address ever reaches disk.

It is committed because every claim above names the run it came from, and several
of those claims are corrections that were only possible because the original rows
were still there. They are **not** a baseline for your own numbers: a rate here is
a reading of the hours it was taken in. `data/runs/README.md` says what each
filename prefix holds and what the masking guard has already missed twice.

**Estimate anything above ~100 requests.** `--dry-run` prices traffic from
per-target constants calibrated by `scripts/analysis/calibrate.py`, each carrying
the run it was read from, and names which targets were measured. Read the hours as
an order of magnitude.

## Reproduce these numbers

Every attempt this repository has made is committed under `data/runs/` as one
JSONL row, and every claim above is a count over those rows. `scripts/analysis/`
reads that directory and nothing else - no network, no credentials, no browser -
and imports only the standard library. A clone and three commands, with nothing
installed and nothing spent:

python scripts/analysis/report.py --all      # the matrix runs
    python scripts/analysis/held.py              # the probe-and-hold runs
    python scripts/analysis/playbook.py          # what to try first, ranked by lower bound

Where each headline lands:

| Claim | Command and section |
|---|---|
| DuckDuckGo, 0 of 50 for the engines announcing the mode | `report.py --all`, `WHOSE FAILURE WAS IT`, the `ddg_serp` block: chromium 0/8 and 0/19, patchright headless 0/9 and 0/14 |
| DuckDuckGo, 95 of 95 for the ones that do not | `PASS RATE`, the `ddg_serp` column: camoufox 7/7 and 37/37, obscura 34/34 and 10/10, patchright headful 7/7. The winning side reads here rather than in the block above, because Obscura records no HTTP status and is absent from every served-versus-refused split |
| For Google the address is the whole of it | `WHOSE FAILURE WAS IT`, the `google_serp` block. `P(live)` is the address and `P(pass\|live)` is the engine, and it is the second column that does not move |
| Amazon used to invert it | same block, `amazon_search`: camoufox live on 47/48, 42/42 and 25/25, against no Chromium-family cell above 33%. This is the August workstation reading and it is the one that did not survive |
| Amazon no longer separates the engines | `report.py data/runs/benchmark_20260819T055927Z.jsonl`, the `amazon_search` block: chromium 419/436 live at 100% pass, camoufox 431/446, patchright 313/457. Read this one against the row above - the two are six days and one machine apart, and the notebook keeps both |
| The hold is real | `held.py`, `HOW LONG A GOOD EXIT LASTS`: 96%, 98% and 99% at positions 2, 3 and 4 |
| One page of warming moved nothing | `held.py`, `BY WARM-UP`. The 75% an operator mentioned is not a before-and-after pair, so this cell is read against its own denominator and against nothing else |
| Geo alignment costs yield | `held.py`, `BY GEO ALIGNMENT` |
| The unanswered-CONNECT floor | `report.py --all`, `DID THE RUN MEASURE THE TARGETS OR THE PATH TO THEM`: 23% of proxied attempts against 0% direct. Read the third caveat before reading that as anyone's - the cause turned out to be in the harness's own traffic |

Four caveats the tools print and a table cannot:

- **Pooled is the weaker reading.** `report.py --all` pools runs from different
  weeks into a number belonging to neither. It says so at the top and marks every
  incomplete cell; one file is stronger: `report.py data/runs/<file>.jsonl`.
- **`unmeasured` is not zero.** A cell stopped by ten burned exits in a row was
  never served a body, so it carries no observation of the engine at all. Printing
  0% there would hand the pool's condition to the framework, which is why the
  DuckDuckGo losers are quoted out of the served block and not the pass-rate table.
- **The CONNECT floor was the harness's own traffic, and every row above it
  predates the fix.** 23% against 0% put the failures on the proxied path rather than on a
  flaky local link, and a second machine on another line in another datacentre
  read 25%, which looked like proof that the path was the provider's problem. It
  was not that simple. HTTP proxy authentication is challenge-response, so a
  browser handed credentials opens the **first CONNECT of each session without
  one**, takes the 407 and retries; the gateway counts unauthenticated requests
  per address and bans on a threshold. At one session per attempt the harness
  generated one such CONNECT per attempt and banned itself, on both machines
  equally - which is why a second network could not see it. Measured inside one
  uninterrupted run either side of the gateway-side fix: `ERR_EMPTY_RESPONSE`
  207 of 1131 attempts before, 1 of 1004 after. `probes/proxy_auth_shape.py`
  reproduces the client half against a proxy on loopback and spends nothing.
  Full account in `NOTEBOOK.md`.
- **`held.py` with no argument pools every probe-and-hold window**, where
  `NOTEBOOK.md` quotes the three that varied geo. The aligned arm is the same 45
  probes either way; the unaligned arm picks up rows from windows where geo was not
  the axis and reads 42% rather than 46%. Direction survives, magnitude moves.

The aggregator is optional. The format is one JSON object per line and the columns
are defined by `ROW_FIELDS` in `nmbench/engines/base.py`, so counting something is
five lines. The DuckDuckGo split, from scratch:

```python
import collections, glob, json
tally = collections.Counter()
for path in glob.glob("data/runs/benchmark_*.jsonl"):
    for line in open(path, encoding="utf-8"):
        row = json.loads(line)
        if row.get("target") == "ddg_serp" and not row.get("direct"):
            tally[row.get("engine"), row.get("headless"), row.get("verdict")] += 1
print(sorted(tally.items(), key=str))
```

That prints camoufox 44 `ok`, obscura 44 `ok` and patchright headful 7 `ok` with
no refusal between them, against 27 and 23 `captcha` for the two headless Chromium
cells with no pass between them. 95 and 50, straight out of the rows.

`peek.py <file>` prints one line per attempt for reading a single run by hand.

Two things are deliberately not checkable. **The bodies are not published** -
gzipped into gitignored `data/artifacts/`, because exit addresses turn up in
embedded links. And **exit addresses are recorded as their /24**, because a
residential pool is other people's home connections. No analysis reads a full
address back out, so nothing above depends on the masked half.

If a number cannot be traced back to a run, it does not belong here.

## Repository layout

```text
nmbench/                     the reusable package - this is what gets published
├── config.py                credentials from .env, per provider, on first use
├── providers.py             loads data/providers/*.toml: one gateway's dialect each
├── proxy.py                 username DSL builder + client-side validation
├── gateway.py               CONNECT probe, exit address lookup, /24 masking
├── relay.py                 local authenticating CONNECT forwarder + byte counter
├── breaker.py               circuit breaker, one per matrix cell
├── console.py               keeps progress output from killing the run
├── matrix.py                cells, round-robin scheduling, resume, cost estimate
├── queries.py               loading the committed query lists
├── blocking.py              resource blocking presets, byte counters
├── targets.py               url building + content-based verdicts
├── stats.py                 the Wilson interval every rate here is quoted with
├── sink.py                  JSONL output, one file per run
├── artifacts.py             gzipped response bodies, so a verdict can be re-read
├── __main__.py              python -m nmbench <command>, one entry point
└── engines/                 one module per framework, one shared contract
    ├── base.py              the row schema and the contract every engine implements
    ├── http.py              plain requests client, the no-browser control
    ├── chromium.py          unmodified Chromium (the control) and Patchright
    ├── camoufox.py          patched Firefox over Playwright
    ├── cloak.py             patched Chromium handing back a Playwright browser
    ├── rebrowser.py         a Playwright fork patching the Runtime.enable leak
    ├── obscura.py           Rust browser with its own renderer, over CDP
    ├── seleniumbase.py      Chrome over ChromeDriver, the WebDriver family
    ├── zendriver.py         Chrome over raw CDP, no WebDriver and no Playwright
    ├── botasaurus.py        Chrome over raw CDP, a second one, for the 2x2
    └── curlcffi.py          scriptless client wearing Chrome's ClientHello

scripts/                     README: which of these can spend money
├── benchmark.py             the matrix runner: engines x targets, one time window
├── probes/                  one file per question, each cheap and single-purpose
├── analysis/                aggregation over data/runs/, sends nothing
└── tools/                   generators for committed inputs

data/
├── providers/               README: one .toml per gateway, and why it is not code
├── queries/                 README: committed inputs, one seed, two lists
└── runs/                    README: masking, filename prefixes, how to read a row

docs/                        README: quickstart and the two findings write-ups
tests/                       offline suite: verdicts, scheduler, DSL, hygiene
```

Every folder a reader lands in from the file list has its own README, because a
directory listing on GitHub is where navigation actually starts.

The split between `probes/` and `analysis/` tells a reader at a glance which files
can spend money: anything under `analysis/` only reads `data/runs/`. A probe that
happens to send nothing says so, and `python -m nmbench` marks it `[offline]`.

## Contributing

`CONTRIBUTING.md` has the rules that are not obvious from the code, most of them
there because the instrument has already been broken that exact way by a commit
that passed every test at the time. The two that catch people first: do not harden
the unmodified control, and nothing branches on an engine, provider or target name.

When adding an engine, a target or an experiment: keep the variable under test
explicit, record enough to reproduce the result, do not compare runs from
unrelated time windows, keep target refusals separate from harness and transport
failures, add offline tests for classification and scheduling, and regenerate the
derived blocks rather than editing a generated number by hand.

The most useful issue you can open is that a number here is wrong. Bring a
denominator.

pip install -r requirements-ci.txt
    make check          # ruff plus the suite: offline, no credentials, no browser

proxy-benchmark

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README