Sessions are currently stored in Redis, a highly-optimized in-memory store with request latency reportedly on the order of ~1 ms. Given the nature of the proposed session storage service, latency can only be higher than what we're accustomed to; It seems implied that we are striking a bargain to trade away some latency in return for multi-master replication, but have not yet agreed upon a price.
We should to establish an SLA for the proposed session storage service.
| SET,GET | mean latency | 50ms |
| SET,GET |90p latency | 100ms |
| DELETE | mean latency | 75ms |
| DELETE | 90p latency | 125ms |
| SET | errors | !!N!!/s|
| GET | errors | !!N!!/s |
| DELETE | errors | !!N!!/s |
NOTE: [[ https://www.mediawiki.org/wiki/Requests_for_comment/SessionStorageAPI#delete | `DELETE` ]] may need it's own latency SLA since its proposed consistency semantics requires a quorum of nodes spanning data-centers.