News for hackers. Stuff that matters.
Re:Flash Memory Wear Killing Older Teslas Due to Excessive D... by catalogia on Tuesday October 15, 2019 @01:58PM (#21261548)
Estimating log growth rate is troublesome. It might be easy enough to measure under normal operating conditions, but sometimes something breaks, maybe a sensor goes bad, and all of a sudden you're spamming your logs at 10,000x the normal rate.

Assuring yourself that under no circumstance is that possible can sometimes be tricky.

Re:Flash Memory Wear Killing Older Teslas Due to Excessive D... by com2kid on Tuesday October 15, 2019 @02:51PM (#21262238)
> maybe a sensor goes bad, and all of a sudden you're spamming your logs at 10,000x the normal rate.

Sure, but sensor error reporting frequency should also be documented and calculated somewhere. Embedded requires more planning, this stuff isn't like AWS instances where the worst case is a larger bill.

And from the sound of it just general usage is causing problems.

Re:Flash Memory Wear Killing Older Teslas Due to Excessive D... by perl4ever on Tuesday October 15, 2019 @07:04PM (#21264987)
If you have a log for something with an indefinite lifespan, and no maintenance of it possible, and a finite storage medium, why wouldn't you just make it circular?

Reminds me of some people's aversion to auto-killing processes when the OS runs out of memory, as though it could ever be better to lock up completely.