SSD Write Endurance 25nm Vs 34nm

[One_Hertz]

Any update on the Sammy ? Did johnw send it off already to Ottawa ?

It is on its way to me via USPS.

[Ao1]

It is on its way to me via USPS.

Hi One_Hertz, did you find anything interesting on John’s SSD? Are you able to determine the P/E cycle count at a block level? (I’d be really interested to find out how the wear was distributed over the blocks).

[johnw]

Hi One_Hertz, did you find anything interesting on John’s SSD? Are you able to determine the P/E cycle count at a block level? (I’d be really interested to find out how the wear was distributed over the blocks).

I doubt he has it yet. I didn't overnight it. It is going by USPS priority mail, which I don't think gets particularly expedited through Customs. I shipped it on Oct 6, but as of Oct 9, it had only made it to LA. I'm not sure if it is going through Customs in LA, (does Canada even have an LA Customs facility?), but if it is not going through Customs in LA, it is certainly traveling slowly.

[johnw]

I doubt he has it yet. I didn't overnight it. It is going by USPS priority mail, which I don't think gets particularly expedited through Customs. I shipped it on Oct 6, but as of Oct 9, it had only made it to LA.

"Your item is being processed by customs in CANADA at 6:49 pm on October 12, 2011."

I love how specific the USPS tracking information is. It is in "CANADA". That really pinpoints its location! At least it is in the right country...

[Ao1]

Here is a graph that shows the relationship between WRD (B1) & MWI (E7) for each of the SF drives being tested (excluding Vapor’s as there is not enough info). Anvil’s drive is holding up significantly better than SynbiosVyse & Christopher’s drives.

On SynbiosVyse’s drive the B1 value is more or less a perfect inverse of E7. I don’t know what NAND is being used in each drive, but it looks like SynbiosVyse & Christopher have NAND with 3K P/E specs and Anvil has 5K. It looks like the “disconnects” that Christopher experienced allowed better wear levelling, which has decreased the MWI burn out rate in comparison to SynbiosVyse's drive.

I can’t help think that SynbiosVyse’s drive failed due to the difference between least and most worn blocks, which resulted in an insufficient reserve block count. I think that is why the drive failed, but why, with hardly any static data, was SynbiosVyse’s drive unable to level out the wear.

@ Anvil, a summary in the first post of each drive being tested along with the NAND P/E specs would be really helpful. Also keys findings and calculation methods would be great.

SynbiosVyse WRD (B1) & MWI (E7)


Anvil/SynbiosVyse/ Christopher

[Christopher]

Here is a graph that shows the relationship between WRD (B1) & MWI (E7) for each of the SF drives being tested (excluding Vapor’s as there is not enough info). Anvil’s drive is holding up significantly better than SynbiosVyse & Christopher’s drives.

Well, the Mushkin is 25% faster than the Force 3 but only half the capacity. Remember, the Force 3 is 120GB(111GB) while the Mushkin is 60GB(55.5GB).

The 32nm Toggle nand in the Mushkin is 5000pe rated and the async nand in the two Corsairs is 3000pe rated.



EDIT
B.A.T.,
is the M4 running with no static data?

You have 100 percent free space there.

[Ao1]

Well, the Mushkin is 25% faster than the Force 3 but only half the capacity. Remember, the Force 3 is 120GB(111GB) while the Mushkin is 60GB(55.5GB).

The 32nm Toggle nand in the Mushkin is 5000pe rated and the async nand in the two Corsairs is 3000pe rated.

Thanks for confirming that. The differences in MWI and B1 are huge. It annoying that the F3 and Mushkin experienced issues, as it’s now hard to know why the outcomes are so different.

Here are comparative B1 and MWI values at ~146K writes to NAND:

Anvil: MWI: 63, B1: 54
(Corsair F3 120GB (25nm) SF2281)

Christopher: MWI: 22, B1: 9
(Mushkin Chronos 60GB (34nm toggle) SF2281)

SynbiosVyse: MWI: 10, B1: 102
(Corsair F40-A 40GB (25nm) SF1222)