Tony of OCZ's marketing staff has this to add:
Richards big issue is he came to support staff for info when he should have gone to marketing....he does this every time and really needs to learn its not how things are done when you are reviewing for a top site. If you are just a forum poster then you go where you need to to get the info you need, when you transition to a reviewer things change....he has lessons to learn imo.
Also he still does not fully understand how these drives work,like most he feels SSD's have to all work in exactly the same way, so fixed variables can be tested and reported upon..Vtx4 is way way different, its built for volume testing only, no RAW, its built with multiple modes of operation that enhance what the drive delivers BUT there are rules...and the best part is the normal end user will always fall within these rules if the drive is used normally. You review it, you test it outside these rules and you will find what he found....totally normal and expected from OCZ's point of view.
As Ryder posted further down this thread,
Before 1.4 the 128's writes were 210MB/s, now with the newer firmware they are 400MB/s before the "storage mode" kicks in (after 50% of the blocks are written to all in 1 go). So most of the time you get higher writes, we could go back to the 210 and leave it there all the time
So we give you all a massive speed increase as long as you stay within the rules...go out of the rules and you will see a speed drop, but you have to do really silly/weird things to go out the rules which a normal end user will never do.
Part of this mode is the reason you get 400 at all. This is a 2 edged sword, increased performance, but more aggressive GC when you get to a write that is 50% of available blocks.
This mode (more aggressive garbage collection) requires processing cycles from the controller, hence it writes the data slower as it performs GC. Before 1.4 we didn't have this and the controller wrote slower all the time.
so you write to the drive filling over 50% of the available blocks, the SSD processor enters its aggressive GC mode, its working harder....BUT you continue to push writes from it as you are benchmarking it...of course its going to show a slow down.
If you fill a drive to over 50% in 1 go or use up over 50% of available free clean blocks then let it do its thing while surfing the net or typing emails etc the drive enters AGC, does it thing, and then settles back down to be near 100% as fast as it was before. So without looking for the issue you never see the issue... its really that simple.
I feel you all have enough now to deduce exactly what is going on here....the short of it is this, do not look for issues, they are not there unless you look really very hard for them and by that i mean create them.
Maybe Tom's should just withdraw the article now and start over again, eh?