Recognises synchronous replication over too long a distance
"Synchronous" across a distance where latency forces asynchronous behaviour or unacceptable write latency.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 66% | Not shown |
| gemini-3.5-flash-lite | Low cost | 54% | Not shown |
| gpt-6-luna | Low cost | 54% | Not shown |
| claude-haiku-5-5 | Low cost | 66% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The defect named on the synchronous replication beyond latency limits, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DS-003 synchronous to a site 420 km away, RPO 1 min Acceptable: Synchronous within metro distance, or asynchronous with the real lag as RPO
Also known as: Synchronous replication over too long a distance
Related knobits
Builds on
All 14 knobits of Plan backup, recovery and continuity.
Source: Review checklist 03-backup-recovery-continuity, row 6 (27031)