Multiple ChoiceBeginner 45s
Sliding window log memory cost
A sliding-window-log rate limiter stores a timestamp per request. What is its main drawback at high scale?
Options
- 1Memory grows with the number of requests in the window per key, which is expensive for high limits
- 2It cannot enforce per-user limits, because storing per-request timestamps makes keying the log by a user ID impossible
- 3It is always less accurate than fixed windows, since counting timestamps is coarser than counting totals
- 4It cannot run in Redis, because the sorted-set operations it relies on are unsupported by Redis's single-threaded model
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.