twitter/fatcache
Memcache on SSD observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4991
- days_rel: n/a
- days_push: 1766
- n_releases_24m: 0
Adoption not part of the score
1299 stars · 173 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Fatcache is a networked, memcached-protocol-compatible cache that uses SSD storage as an extension of DRAM, allowing terabyte-scale caching at lower cost. It batches small writes to avoid SSD write amplification and is now retired in favor of Twitter's Pelikan.
Use cases
- cache large datasets that don't fit in memory
- reduce DRAM cost for terabyte-scale memcached workloads
- run a memcached-compatible SSD-backed cache
- maintain high cache hit rates for big data workloads
- extend an in-memory cache tier with SSD capacity
When to choose
- you need a memcached-protocol cache larger than DRAM allows and can accept slightly higher latency
- you want lower cost per cached byte than pure in-memory caching
When to avoid
- you need actively maintained software - the project is retired
- your working set fits comfortably in RAM
- you need persistence - fatcache is still a volatile cache
- consider Pelikan or modern alternatives instead
Facets
service · maturity abandoned
caching database databases performance backend big-data c self-hosted memcached-protocol ssd-cache distributed-cache key-value-store retired linux
1 source
- readme: https://github.com/twitter/fatcache · fetched 2026-08-28 · 9b9807c4eb28
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| twitter/fatcache | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="twitter/fatcache")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem