This is maybe a question for Garmin itself, but I have been wondering whether the use of the Storage.set() method in a background delegate onTemporalEvent() call with a 5min rate would cause premature wear out of the watch flash storage? For example maintaining an array through permanent storage that has the last 500 values (48 hours worth of data) for some fields in floating point could cause up to 4 sectors to go through P/E erase cycles every 5 min. Is the NAND system handling wear leveling or handling this via caching and deferred write cycles? Has anyone experienced issues with making too many persistent storage writes over time?
