You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All code block are disabled, so it never sync in this way anymore.
It stores data in very inefficient way. for 256KB hdd with 32 blocks it will make 8192 .txt files in data/wireflash, each file are 744 bytes to store just 128 bytes real data. I think block should be higher to reduce that, and instead of storing using string.rep(" ",24-string.len(floatstr)) it might write data as binary. Also it even can use compression to save space.
Writting speed are slow, only 128 bytes per sec (32 blocks x 0.25 sec think func), so full capacity of 256kb will be written by 2048 seconds ~34 minutes. There is fallback on entity remove, which flushes all content instantly to disk, but making lag if there is a lot of data left.
Describe the bug
This is very old story from #1338 (comment)
Look here:
wire/lua/wire/stools/hdd.lua
Line 80 in 61691f7
All code block are disabled, so it never sync in this way anymore.
It stores data in very inefficient way. for 256KB hdd with 32 blocks it will make 8192 .txt files in
data/wireflash, each file are 744 bytes to store just 128 bytes real data. I think block should be higher to reduce that, and instead of storing usingstring.rep(" ",24-string.len(floatstr))it might write data as binary. Also it even can use compression to save space.after re-paste it i have data loss, there is CRITICAL issue with not writting last index from cache! created pull wire EEPROM doesn't write last index from cache! #3696 separately
Writting speed are slow, only 128 bytes per sec (32 blocks x 0.25 sec think func), so full capacity of 256kb will be written by 2048 seconds ~34 minutes. There is fallback on entity remove, which flushes all content instantly to disk, but making lag if there is a lot of data left.
How to reproduce the bug
No response