Closed Bug 1415634 Opened 7 years ago Closed 7 years ago

Increase quota sizes for Kinto WE Stack to reduce HTTP 507 responses

Categories

(Cloud Services :: Operations: Kinto, task)

Product:
Cloud Services
Component:
Operations: Kinto
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mostlygeek, Assigned: bobm)

References

Details

The quotas currently set for the Web extensions kinto stack do not account for encryption/base64 encoding overhead. Currently it is set exactly to the values defined by the storage.sync spec [1]: - quotas_bucket_max_bytes_per_item: 8192 - quotas_collection_max_bytes: 102400 These settings should be doubled: - quotas_bucket_max_bytes_per_item: 16384 - quotas_collection_max_bytes: 204800 [1] https://developer.chrome.com/extensions/storage#property-sync
See Also: → 1413949
I pulled the record sizes for "Insufficient Storage" messages from a 2hr packet capture on a single production webhead. Here is an R summary of the result: Min. : 8201 1st Qu.: 12367 Median : 12559 Mean : 37177 3rd Qu.: 31759 Max. :1326183
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Looking at the metrics it looks like we've reduced the rate of 507's by 60%
You need to log in before you can comment on or make changes to this bug.