Claim checker benchmark
When a player claims, a claim checker has to decide whether the claim holds however the unseen cards lie, not just with every card on view. This page times bridge-solver's claim checker on a fixed set of claims, in your browser. Every device runs the same claims, so your result can be set beside anyone else's, and beside the native tool below.
Loading the engine…
| Workload | Cards | V | X | ? | Nodes | ms | ms/claim | Verdicts | Native |
|---|
The workloads
- rest-dd
- "The rest are mine." Declarer's side has the high cards and is on lead, and double dummy takes every trick; declarer claims them all. This is the claim players make.
- strong-dd
- Declarer's side has the high cards and claims the double-dummy number of tricks.
- decl-dd, def-dd
- Random hands, with declarer or the opening leader claiming exactly the double-dummy number. The hard case: these fail only when the claimer would have to guess.
- decl-all
- Random hands, declarer on lead claiming every trick. Nearly all are bad claims.
Each claim is V (valid), X (invalid) or ? (the search ran out of its node budget, so the claim is rejected, as BBO's checker does). Verdicts and node counts never depend on the device, so they are checked against the native tool's; only the times should differ. Only the checking is timed, not generating the claims.
Next: every core, natively
This page uses one thread of your browser. The native bridge-claim tool runs
the same claims on every core, faster per core too, and can check claims of your own.
Download it for your system from the
latest release
(bridge-claim-macos-aarch64, -macos-x86_64,
-linux-x86_64 or -windows-x86_64.exe), then run it from a
terminal:
bridge-claim bench # every workload, 7 to 13 cards, all cores bridge-claim bench --preset quick # the same claims as this page's Quick run bridge-claim check claims.txt # your own claims; --help gives the format
The downloads are not signed. On a Mac, clear the download flag first with
xattr -d com.apple.quarantine bridge-claim-macos-aarch64 and
chmod +x it; on Windows, choose "More info", then "Run anyway".
Everything runs on this device. When a run finishes, the page records an anonymous
summary: how long it took, how many claims, and your browser and system family, with no
identifier of any kind. Add ?nolog to the address to turn that off.
Privacy · Statistics ·
Double-dummy analysis