Wow, did not know that wear leveling was built in. Can I assume that in addition to the wear leveling writes will use “update” so they only write if there is a change?
I don’t see any issue with saving hourly or daily data as even without wear leveling, these would last for years.
My question is in trying to judge the life of the device when I store the current state.
If I have a device that stores its “state” including the current counts and would be an object like this:
- Control register (byte)
- hourly count (2xbyte)
- daily count (2xbyte)
- time stamp of last count (4xbyte)
- alerts (byte)
- resets (byte)
For a busy park this object would be updated about 2,000 times a day. Without understanding the effectiveness of the wear leveling program is, how can I estimate the useful life?
That said, I have interacted enough with you on the forum to trust what you say. If there is no easy answer other than “trust the algorithm” I can be OK with that since Flash storage is quite mature and the wear leveling issue must be much more of an impact on devices such as PCs and Servers.