Catalogue

Cards
165
Records
486
Workloads
19
Corpus version
74847648e25a
Workload
Kind
Setup

8 of 486 records match.

KindRecordOrganisationYearSetup
Failure

Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them

bluesky-2025-lossy-timelines#f1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines

bluesky-2025-lossy-timelines#d1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Cache high-follow accounts in a Redis sorted set loaded into memory every 30 seconds instead of reading follow counts per write

bluesky-2025-lossy-timelines#d2peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Scale ZippyDB keyspaces online via logical-to-physical shard indirection and coordinator-worker resharding

meta-2023-threads#d1

Meta2023Sharded
Decision

Offload Instagram-to-Threads follow-graph mirroring and notifications to rate-limited Async workers

meta-2023-threads#d2

Meta2023Sharded
Failure

Database contention filled Redis memory, and a full Redis could neither accept nor release jobs

slack-2017-job-queue#f1peak under 100,000 requests/s

Slack2017Sharded
Decision

Added Kafka in front of the Redis job queue instead of replacing Redis

slack-2017-job-queue#d1peak under 100,000 requests/s

Slack2017Sharded
Decision

Enqueue path acknowledges after the Kafka leader only, trading a small risk of lost jobs for latency

slack-2017-job-queue#d2peak under 100,000 requests/s

Slack2017Sharded