How do P/E cycles work in terms of total writes on SSD?

Soldato
Joined
27 Oct 2005
Posts
13,804
Location
Netherlands
Hello,

As per title, we are in a dispute more or less with a retailer that supplied half-size m-sata ssd's. These are 32gb MLC SSD's, with 3000 p/e cycle limit.

Is it as simple as 32gb * 3000 = 93,75TB? How much writes can we use effectively on this SSD?

Because the manufacturers tooling shows values between 5000-6000 (depending on the specific example) ''average erase count'' out of 3000 (P/E Cycle limitation) on SSD's after a year of use.

We don't write anywhere near 90 TB per year (more like ~0.9tb/year in the worst case, let alone 180TB)...

EDIT: I can see Write amplification is a factor, how do you calculate/establish the write amplification?
 
Last edited:
What OS are you using (and is TRIM supported/enabled)?

If there is no TRIM support, then write amplification will be causing whole pages to be erased, potentially burning through your p/e cycles.

https://en.wikipedia.org/wiki/Write_amplification

W10 Ent. LTSB Retail

Trim is enabled, but not supported.

After the first 100, we switched from SSD model, the new one does have trim (but I have no tooling to read the smart data yet).
I am not sure how much data is written exactly, but it is between 10kb/sec to 30 kb/sec on average. Both model SSD's don't log data written :(. (OR well I'm not sure about model/brand #2, because we don't have tooling yet to read all the SMART Values yet. Tools like SSDlife are useless because they don't recognise the both the SSD's.)
 
Last edited:
Does anyone know how to read out the SMART data/calculate SSD life?

The new SSD's we use are industrial Transcends, we need SSD Scope Pro as the consumer version of SSD scope does not read these.

SSDlife is utterly useless, all ''unknown attributes''.
Crystaldiskinfo does show the Reads and writes, however, the raw values don't tell me to much (don't know how to interpret these values) nor do I know the limit of these. And there are many ''vendor specific'' fields too.
 
Last edited:
Write amplification could be as bad as 64x fold e.g. write 4KB of data (i.e. a page), but if there are no free pages then an erase operation is needed which works in blocks of 256KB (i.e. 64 pages).

Values are just examples based on that Wikipedia article, but should give you some idea of how bad not having TRIM potentially is.
 
OK, GSmartControl can read the writes/reads, they're logged in LBA's.


I can't find a specsheet of the 32gb version we have, but the max LBA for the 128gb version is :
User Max. LBA
250,069,680

Is this the same for the 32gb, or do I have to divide by 4?
 
Back
Top Bottom