Not sure what numbers you looked at.
The ones in your link.
Specifically the sequential write numbers- because that's what the cameras would be doing in a Tesla.
See the attached screenshot from the website. These are all very fast (relatively) cards and 4 of them don't get past 4MB/s.
Yeah- that's RANDOM writes.
Which isn't, at all, what the car does.
When people talk about sequential vs random writes to a file, they're generally drawing a distinction between writing without intermediate seeks ("sequential"), vs. a pattern of seek-write-seek-write-seek-write, etc. ("random").
Random writes are things where a program (or more likely many running-at-same-time programs) have to seek random files and update them regularly.... existing game data, database contents, etc...
Part of the reason THAT gets
Not, in any way, relevant to this application....The car writes static 30MB files per minute per camera.
It's NEVER "updating" an existing file... so it's NEVER doing a random write that takes that kind of performance hit.
We have argued before that we are not sure how Tesla writes to the flash drive to be sure we should be looking at sequential speeds only.
I'm pretty sure...because nothing the software does requires random writes.
You'll also note that the "bad" random write results are usually found when writing TINY files... like 4k size files...not 30MB sized files.
This makes things look far worse than they are because of how page size works on flash...it's essentially an absolute worst-case-scenario benchmark....and again it's not something that'd be at all relevant on the Tesla where it's never updating an existing file, and it's never writing TINY bits of data.
Further, as others have mentioned, most tests are done on empty or near empty drives/cards so that's the highest numbers you can get. Once a drive is getting full it needs to do extra work which can cause severe slowdown.
Man- if only I'd mentioned the
exact issue of flash slowing down when near full.... oh, wait... I did.
But even then you don't see impact until it's like 70-80% full at least and it's not usually a major issue till ~90% or more.
But yes at that point it's an issue for ALL flash media... so just clean your storage out every few months- problem solved.
N
Good part is toward the bottom. Forget this is old article, it is actually somewhat worse nowadays wit TLC and higher density cells.
The SSD Anthology: Understanding SSDs and New Drives from OCZ
Amusingly, this confirms exactly what I JUST told you...
Your source said:
And therein lies the problem, the smallest structure you can erase in a NAND flash device today is a block. Once more, you can read/write 4KB at a time, but you can only erase 512KB at a time.
That's why -4k- random writes are slow.
It has to ERASE 512kb at a chunk to update/write that tiny 4k
But in this case the files being written are always MUCH larger than 4k OR 512k...it can easily write in full blocks so you're not taking that huge penalty over and over even if it WERE doing random writes (which again it's not)