Loading…
How records move: the rules they meet, the queue, how long it takes, and the scrapers that feed it. Open any record to see its own way through.
How long a source record takes (its latency), from when its source submits it until readers can see the curated result. Measured end to end by api.coop, and per stage by the rules runner.
Submit to visible, end to end
Listed in api.coop
From when the author submitted a record (its createdAt) to when api.coop could list the curated record, over the last day. The delay from the author's PDS to Jetstream, the rules and indexing are all inside.
1,791 records measured.
2 records carried a submit time after it became listable (a wrong clock) and are not counted.
414 records listed in this window were submitted earlier (a backfill) and are not counted.
Submit to visible, as the rules runner sees it
Without moderation
Listings that show a record once it is curated.
median (half are faster)95th percentile (all but the slowest 5%)
2,598 records measured.
With moderation
Listings that wait until the rules after the merge have labelled it.
2,554 records measured.
A chain request runs every rule for one record at once; a cluster lock is held while the curator rewrites one cluster.