- From: Eriko Kurimoto <notifications@github.com>
- Date: Mon, 19 May 2025 23:09:53 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 May 2025 06:09:56 UTC
elkurin left a comment (w3c/ServiceWorker#1770) About the size limitation, 4GB is one obvious choice considering int32_t maximum size, but might be not enough considering we already have 2GB+ usage. In the existing Chromium implementation, we support ~256GB (while it has some bug still) [ref](https://source.chromium.org/chromium/chromium/src/+/main:net/disk_cache/simple/simple_index.h;l=94-109;drc=2b35bf22bd0880940599f0d677a45891d252ef4a). We rounded up to 256 bytes blocks to hold ~256GB values in int32_t where we picked 256 bytes as a common alignment. So, I proposed 100~200 GB as somewhat satisfying and supportable size. Tests are another concerns. As @asutherland pointed out, tests with large file s not ideal, and also it won't fit in the maximum time duration in WPT. Anyway, I opened a new issue in storage spec: https://github.com/whatwg/storage/issues/181. Sounds better to continue discussion there. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1770#issuecomment-2893075081 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1770/2893075081@github.com>
Received on Tuesday, 20 May 2025 06:09:56 UTC