there is several limits. But I could say that 10MB+ can lead to issues.
76MB file size is dangerous and can create data corruption
InvitationNotFound wrote: »
InvitationNotFound wrote: »
I guess in this case, the post you quoted is the source. If you are not aware, Ayantir is the developer of Skyshards, Lorebooks, Destinations etc.
If you want another addon dev to confirm the save file issue: I can also confirm from bug reports on my addon HarvestMap (another very data heavy addon like PriceTracker), that the game sometimes just stops writing to the save file halfway through, if it gets too large.
If you want another addon dev to confirm the save file issue: I can also confirm from bug reports on my addon HarvestMap (another very data heavy addon like PriceTracker), that the game sometimes just stops writing to the save file halfway through, if it gets too large.
InvitationNotFound wrote: »
It's a bit more complicated than this.All SavedVariables are loaded into LUA memory when you log into a character.
If you don't have enough memory, you will get data corruption.
That means that if you run out of LUA memory and you log out, your SavedVariables file *will* be corrupt!
At that point, it would be better to kill the ESO process and not log out.
All SavedVariables are loaded into LUA memory when you log into a character.
If you don't have enough memory, you will get data corruption.
With a file that big, you need to bump up your LUA memory, which you can do from the general ESO settings file, can't remember the exact name of the entry (at work right now) but it says something about LUA and memory.
Again, whenever you log into a character, all AddOns enabled for this character will be loaded into memory along with their respective SavedVariables files and the SavedVariables will be written back to file when you log out to the character select (or /reloadui).
That means that if you run out of LUA memory and you log out, your SavedVariables file *will* be corrupt!
At that point, it would be better to kill the ESO process and not log out.
InvitationNotFound wrote: »
Me, I and Myself. And I know more on ESO SavedVars than anyone here. If you don't believe me, no problem, I'm accustomed.It's a bit more complicated than this.All SavedVariables are loaded into LUA memory when you log into a character.
If you don't have enough memory, you will get data corruption.
That means that if you run out of LUA memory and you log out, your SavedVariables file *will* be corrupt!
At that point, it would be better to kill the ESO process and not log out.
You can have a savedvar corrupted without any Lua Memory issues.
And I would say that 64bits client and few internal reports almost fixed all the cases. But it can still be possible.
--
The guy who played with thoses issues 2 years ago.
I'm the author of several AddOns, so yeah, it pretty much works that way.InvitationNotFound wrote: »i don't think it works like that.
@Philgo68
So ZOS did away with the LUA memory setting? Because i still have it in my settings file ...SET LuaMemoryLimitMB "512"
sylviermoone wrote: »Per Chip Hilseberg, the error was purely informative. It also never needed to be updated, as it's my understanding that LUA memory always auto-expanded to the user's need. It was removed with the Morrowind update.@Philgo68
So ZOS did away with the LUA memory setting? Because i still have it in my settings file ...SET LuaMemoryLimitMB "512"
http://www.esoui.com/forums/showthread.php?t=6985
I'm the author of several AddOns, so yeah, it pretty much works that way.InvitationNotFound wrote: »i don't think it works like that.
The LUA memory in ESO is separate from the normal application memory, so yes, you can easily run out of LUA memory with the default settings if you have AddOns that load large SavedVariables files or are otherwise memory intensive.
In that case, you came to the wrong place. The only people who can give you that information work for ZOS.InvitationNotFound wrote: »Anyway, I'm still waiting for some technical background information instead of some wild assumptions, which didn't really explain anything at all or were simply wrong.
Reorx_Holybeard wrote: »Its hard/impossible to say from just a short file snippet although it looks like the file is reasonably structured. When you say it "doesn't load it" what exactly do you mean? Do you get a UI error, game crash, the addon doesn't work? If it was truly a corrupt saved variable file then I would expect the large file to be overwritten by a small file when you logout. If that doesn't happen it may be another issue.
The PriceTracker addon hasn't been updated in a year and a half so I would guess it is just broken with the last update which changed some of the API calls breaking MM and our price tracker built into uespLog.
With a file that big, you need to bump up your LUA memory, which you can do from the general ESO settings file, can't remember the exact name of the entry (at work right now) but it says something about LUA and memory.
so iv been using price tracker addon and it stores pricing data that i see on traders into the savedvariables folder.
The file has hit 76.8MB - yeh theres a lot of traders in the game, and ESO doesnt load any of it now.
Is there a file size limit for the stuff in this folder?
how does mm or ttc compare for instance for its variables? dont tell me to simply use them, id rather not. im asking about the savedvariables not what you prefer as a pricing addon.
If author is aware of his data being up to 20 MB HE_MUST_DO_SOMETHING And with 20MB i'm kind, it should be 10MB.
It's not to ZOS to handle the *** of our code.
There is tons of tips and tricks to reduce data length of our addons.
Encode them, Reduce column keys, remove data, drop ZO_SavedVars, it's not hard.
["88996"] = -- BAD TYPE : It should be a number.
{
[210] = -- BAD CONCEPTION If the ItemId cannot determine your final item, it should be at the same level of the itemId
{
[1512770236] = -- BAD CONCEPTION They key is a timestamp ? It should be an ipaired data.
{
["guildName"] = "Azura's Guidance", -- BAD CONCEPTION, use a table and add a key.
["guildId"] = 0, -- UNNEEDED if guildname is set. guildName and guildId should be 1 and only 1 column. 1-5 for user guild 6 to n for non user guilds.
["quality"] = 3,
["purchasePrice"] = 800,
["name"] = "Girdle of the Juggernaut", -- UNNEEDED, you should be able to build the item name from the itemid/link.
["expiry"] = 1512770236, -- BAD CONCEPTION , it's the key. and this is a timestamp. I agree this should be here and the value is OK but we have a redundancy here.
["stackCount"] = 1, -- UNNEEDED. This should only go in sv when qty is > 1
},
I never used this addon, I never looked to its code and I can divide by 50% the length of its savedvar.
If author is aware of his data being up to 20 MB HE_MUST_DO_SOMETHING And with 20MB i'm kind, it should be 10MB.
It's not to ZOS to handle the *** of our code.
There is tons of tips and tricks to reduce data length of our addons.
Encode them, Reduce column keys, remove data, drop ZO_SavedVars, it's not hard.
["88996"] = -- BAD TYPE : It should be a number.
{
[210] = -- BAD CONCEPTION If the ItemId cannot determine your final item, it should be at the same level of the itemId
{
[1512770236] = -- BAD CONCEPTION They key is a timestamp ? It should be an ipaired data.
{
["guildName"] = "Azura's Guidance", -- BAD CONCEPTION, use a table and add a key.
["guildId"] = 0, -- UNNEEDED if guildname is set. guildName and guildId should be 1 and only 1 column. 1-5 for user guild 6 to n for non user guilds.
["quality"] = 3,
["purchasePrice"] = 800,
["name"] = "Girdle of the Juggernaut", -- UNNEEDED, you should be able to build the item name from the itemid/link.
["expiry"] = 1512770236, -- BAD CONCEPTION , it's the key. and this is a timestamp. I agree this should be here and the value is OK but we have a redundancy here.
["stackCount"] = 1, -- UNNEEDED. This should only go in sv when qty is > 1
},
I never used this addon, I never looked to its code and I can divide by 50% the length of its savedvar.
the guild id is not related to the guild name i dont think. i believe its to do with you and your guilds. but i got more stuff to go through yet. i was considering removing it if possible.
1 zone of traders is a couple of MB. i think alikr was like 8MB. its impossible to keep this under 20MB and have a comprehensive list of items for sale.
it has a lot of spaces. it looks in the text file properly formatted for code. but using spaces not tabs. that might cut down a lot. its one thing i havent checked before. it might not support tab though.
The guild id is related to the guild name. It is different for everyone but with the guild name you can determine the guild ID.
While currently alikr might be 8 MB, if you changed stuff, maybe it would be 2-4. There would still be a large saved vars file but it would be smaller.
Addons have no effect on the format of the saved variable tables.