I have asked we try to release some educational material that will help people understand how our drives work better..this is being discussed now.
At 50% capacity there's an internal reorganization routine that's triggered on Vector, similar to what happens on the Vertex 4. During this time, all performance is impacted, which is why you see a sharp drop in performance just before the 135GB mark. The re-org routine only takes a few minutes. I went back and measured sequential write performance after this test and came back with 380MB/s in Iometer. In other words, don't be startled by the graph above - it's expected behaviour, it just looks bad as the drive doesn't get a chance to run its background operations in peace.
under any circumstances the ONLY time you will ever see a slow down is when you write 100% LBA in 1 go...so you are in fact inducing the slow down by looking for it.
I am not actually support, I'm marketing, hence I was focused on you not fully understanding how our drives work and nothing else.
That would be a first. A marketing or sales guy in the tech world actually understanding what he is marketing or selling.
Send me a Vector and I will promote the hell out of it.... Just Sayin'
One guy was able to get max IOPS of 172k for the Vector, compared to 127k for the Samsung 840 Pro... interesting. I know these are Max values so they don't mean all that much but that's quite the gap though.
Either those results are bogus, or else they are 512B reads or writes. If the latter, then it is basically useless, since who runs workloads that are sustained 512B reads or writes at QD32 on an empty SSD?
65.11MBps / (512B/1000^2) = 127,168 IOPS
Yup, the IO size is 512B. I'm guessing those are writes because OCZ has always liked to cache a lot to the DRAM (that's why the Agility 4 gets okay write speeds, but read speeds are horrible).
The agility uses the same controller as vertex3 right?
Buy it has cheaper NAND and that's why it's slower ?
Agility 4 uses Indilinx Everest 2 (i.e. the same as in Vertex 4) but the NAND is asynchronous whereas Vertex 4 uses synchronous NAND.
Either those results are bogus, or else they are 512B reads or writes. If the latter, then it is basically useless, since who runs workloads that are sustained 512B reads or writes at QD32 on an empty SSD?
The point of his post was to point out how much more powerful and capable the Barefoot 3 controller really is.
You don't see many 128GB reviews anymore... I wonder why ?
I'm not sure when the change occurred but there are more 256GB drives being sold now than 128GB drives.