Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Increase maximum item size in Storage sync quotas #510

Open
erosman opened this issue Dec 22, 2023 · 4 comments
Open

Proposal: Increase maximum item size in Storage sync quotas #510

erosman opened this issue Dec 22, 2023 · 4 comments
Labels
follow-up: chrome Needs a response from a Chrome representative topic: storage Issues related to persisting data. Topics include browser.storage, web storage, and new APIs.

Comments

@erosman
Copy link

erosman commented Dec 22, 2023

Proposal: Increase maximum item size in Storage sync quotas

There is already a discussions on increasing the "Maximum total size" from 100KB to 1MB in Discuss limits applied to storage.local and storage.sync API.

This proposal concentrates on the "Maximum item size", as also mentioned in #351 (comment).

Storage quotas for sync data

  • Maximum total size 102,400 bytes (100KB)
  • Maximum item size 8,192 bytes (8KB)
  • Maximum number of items 512

Test Case

Syncing the following example would be within the "Maximum total size" allowed, however it fails due to the "Maximum item size".

The options are:

  • Giving up on storage sync
  • Breaking the large value into smaller values and recompile the data at the sync target
    (which adds undesired complexity to the operation and onChanged event)
{
  "a": "... 1kb data ...",
  "b": "... 1kb data ...",
  "c": "... 50kb data ..."
}

Proposal

Increase the "Maximum item size" to the maximum possible under the "Maximum total size"

See also

@Juraj-Masiar
Copy link

I'm using storage.sync in several of my extensions and I highly support this upgrade.
Although, to be realistic, 1MB may be too big upgrade for browser vendors. I would be happy even with 512KB or 256KB.
The biggest issue for my cases are:

  • the 8KB limit per item, this should be increased to as much as possible (at least 128KB would be great)
  • the 512 items limit, here I would go to 4096 or more, since users sometimes have thousands of notes/bookmarks/favorites, etc...

@Rob--W Rob--W added the follow-up: chrome Needs a response from a Chrome representative label Jan 4, 2024
@Rob--W
Copy link
Member

Rob--W commented Jan 4, 2024

All vendors are against raising the maximum total size, but not immediately opposed to considering to raise the item sizes. Need to discuss internally.

@Rob--W Rob--W added topic: storage Issues related to persisting data. Topics include browser.storage, web storage, and new APIs. and removed needs-triage labels Jan 4, 2024
@dotproto
Copy link
Member

To add a bit of context, vendors are against raising total storage limits because of the impact this would have on their synchronization services. The sync storage area is primarily meant as a way for extensions to share configuration or settings data across logged in browsers. It is not meant as a general purpose storage solution. Developers that need a way to store and sync larger amounts of data should consider standing up their own backends or look into cloud storage solutions.

@hanguokai
Copy link
Member

The original proposal explicitly said: This proposal concentrates on the "Maximum item size", not "Maximum total size". So I will open a new issue for "Maximum total size", and copy related comments to there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
follow-up: chrome Needs a response from a Chrome representative topic: storage Issues related to persisting data. Topics include browser.storage, web storage, and new APIs.
Projects
None yet
Development

No branches or pull requests

5 participants