Skip to content
DBRaven
Cache Simulation

Cache Placement: Steady-State Snapshot

Model how cache capacity, hit rate, hot-key skew, and invalidation pressure split load between the cache and the primary database, and what happens to that load if the cache becomes unavailable. This is a single steady-state evaluation of your inputs, not a time-evolving simulation: it does not model warm-up, traffic growth, or real hot-key distributions over time.

The effective hit rate shown here is computed from your inputs, not an independently measured or predicted production value — treat it as a directional estimate under the assumptions you entered, not a promise about what your real cache will do.

Traffic And Cache Shape

1–1,000,000

Total requests per second to the cached resource.

≥ 1

Total size of data that is actively read.

≥ 1

Cache memory capacity.

0–100

Hit rate before eviction/invalidation pressure is applied.

Latency

0.01–10,000
0.01–10,000

Risk Shape

0–100

Explicit skew toward a small set of keys. Never inferred from request rate — enter what you actually expect.

0–100,000

Cache entries invalidated per minute, modeled directly rather than via a TTL recommendation.

0–100

100 = fully available. 0 = simulate a full cache outage.

1–5

1 = no retry amplification modeled. Higher values estimate clients retrying into an already-degraded database during a cache outage.

No simulation run yet

Configure your cache shape and traffic, then click “Run Cache Simulation”.