QUOTA_BYTES_PER_ITEM

[djmichaelsaler]

When read a lot of GE of a player in console tab flash this message:
QUOTA_BYTES_PER_ITEM quota exceeded
(anonymous) @ storage.js:123
I change syncSet and syncGet by localSet and localGet to fix it.

[veger]

When building this, I checked the quotas and noticed that it looks like the quotas were not 'active'..? (I exceeded them without issues).
But it looks like you found the limits.

As I assumed these limits should have been actually used, I created ways to clean up the data.
If you go to the 'Settings' tab you can clean the data for each world you are active in. (It removed data that is not refreshed in the last 7 days, if I remember correctly)

[veger]

I checked the code, it is 3 weeks.

[paskyorg]

The problem is not QUOTA_BYTES (102,400 bytes), but QUOTA_BYTES_PER_ITEM (8,192 bytes).
With only 9 users and 160 great building in total, the limit of 8,192 bytes is exceeded.

I have added to the syncSet function, this line:
console.log(JSON.stringify(worldItems).length)

And this is the console output: 9065.

[paskyorg]

Either each user becomes an individual key or the limit will easily be exceeded.
Or maybe the best option is to switch to chrome.storage.local with 5,242,880 bytes of quota.

[veger]

Switching to chrome.storage.local might be best solution.
I had the idea to be able to sync the collected data, so independent of your location/device you would have this info available. But it is far too small to keep all info I guess...

[djmichaelsaler]

https://github.com/kdzwinel/Context/blob/master/js/classes/HugeStorageSync.class.js

This is the solution to sync data?

[veger]

You still have QUOTA_BYTES. So it helps a little, but you will pass this (soon) as well.
The chrome.storage.local has a much higher limit, so going for this storage is seems best bet