How big is Host Writes on your SSD?

[One_Hertz]

One_Hertz

ETA for your drive?

Today apparently. NCIX is very fast here in Canada.

I guess we need to come to a consensus on our test parameters so we do the same thing. Are we going to TRIM the drive or not? Some users will use TRIM, others will not due to RAID or due to an OS that doesn't support TRIM.

The whitepaper I linked recommends using QD 1 for endurance testing as higher QD is not necessarily realistic (as Ao1's testing showed as well).

For size distributions maybe 50% static data, 25% test file size, 25% empty? What mix of block sizes do you want to use? As for seq/random I am thinking 70% random?

Are we using IOMeter or are you writing us a utility?

[Ao1]

So we have a 320 & an X25-v head to head?

My vote is for TRIM.

For comparison here are the JDEC xfer sizes for their proposed SSD Enterprise Endurance Workload.

That doesn't seem too far off the mark to what I have seen when monitoring, although I do see larger xfers ~ 1MB and above from time to time. Larger xfers are obviously more application centric, whereas those below are more OS related. I'd vote for a bit of a mix.

512 bytes (0.5k) 4%
1024 bytes (1k) 1%
1536 bytes (1.5k) 1%
2048 bytes (2k) 1%
2560 bytes (2.5k) 1%
3072 bytes (3k) 1%
3584 bytes (3.5k) 1%
4096 bytes (4k) 67%
8192 bytes (8k) 10%
16,384 bytes (16k) 7%
32,768 bytes (32k) 3%
65,536 bytes (64k) 3%

http://www.jedec.org/standards-documents/docs/jesd219

[One_Hertz]

This test will take forever. Such a workload will be very very slow at QD1 on these 40GB SSDs. 10MB/s? I guess we'll see.