Samsung EVO 840 500GB VS OCZ Vertex 4 256GB

I’ve decided to move to a 500 GB SSD to have plenty of space to store my virtual machines. At the time of the decision, Samsung EVO was the better option. I’ve posted in the past benchmarks for my Vertex4 256 GB

And I was really curious about performance of Samsung EVO. Vertex 4 has a real impressive write speed, even if after one year of use if you test it again you can find a decrease in performance. Running test on the Evo gave me these results.


Actually it seems to outperform the Vertex 4 and this makes me really happy, because I feared that the Evo would have been a little slower in writes than Vertex 4, but it seems to be surely comparable. This test was also done with a 500MB file size while the original Vertex 4 test has 100MB file size, for the sake of comparison I decided to run another test with the same 100MB setting, but the result is substantially the same (little standard fluctuation of numbers)

Samsung has also a nice feature in his Magician software for Evo SSD, that can actually use system RAM to further improve performance of SSD. Magician software has also a nice feature to upgrade firmware of the SSD directly from your Windows operating system even if it is system disk. Creating a bootable CD or Usb stick with firmware update program is not a big problem, but pressing a button and having your firmware update is a nice facility.

After updating firmware and some OS optimization suggested by magician software I re-run the test again, just to see if there is anything changed (I’m not expecting any substantial changes). Here is the result if you are curious.


As expected the data are substantially the same, some little fluctuation are quite standard. Then I decided to enable Rapid mode, a technique that uses computer RAM to accelerate disk operations. I perfectly know that such kind of optimization should be tested in everyday use, but I decided to have another run of CrystalDiskMark to understand what happened. Here is the result


I really must admit that I found difficult to really squeeze something out of this numbers, the increment in the diskmark is probably due to how the test is performed and I doubt that this is a “real” improvement in the everyday use, but I’ll leave it enabled just to understand if I’ll perceive some “change” respect having it not activated.

Gian Maria.

OCZ Vertex 3 Vs Vertex4

I own both a Vertex3 256GB and a Vertex 4 256, and people usually ask me if the vertex 4 is really faster than vertex 3, or difference in performance are really little. I think it is difficult to answer this question, I can only post you Cristal Diskmark test for both drive when they are completely empty.

This is the Vertex 3

And this is the Vertex 4


From the test I can tell you that the Vertex 4 has a great increase of performance in Write Speed, and a real gain of performance in 4K QD32 tests. I had also a Vertex 2 and I was really satisfied with performance and reliability of OCZ drive, and I should admit that the Vertex 4 performances are really really huge.

Do not forget that such a drive needs a good Sata controller or you can suffer performance loss, as I described in an old post.

If you work heavily with Visual Studio or you run quite often Virtual Machines, having a fast SSD is a must.

Gian Maria.

Vertex 4 vs vertex 3 OCZ Hard disks

My new Vertex4 SSD is just arrived, I bought essentially to upgrade my laptop that has an old OCZ vertex2 drive 120 GB. I was constantly striving to make room for my virtual machines, so I decided that it was time to upgrade it to a 240GB SSD disk. As soon as my vertex 4 is arrived I immediately upgraded the firmware and run some benchmark


Figure 1: Benchmark of Vertex4 empty drive with firmware 1.5.

Actually it is interesting to compare to the result of the Vertex3 I did some month ago.


Figure 2: Benchmark of Vertex3 empty drive

The results confirmed what I heard on various forums, it is actually slower in sequential reading but it is faster in random tests, and sequential write. Actually this is a good balance because I rarely have big sequential file to read, instead I always want random write speed to maximize compile time in Visual Studio.

I’m happy of the test, even if probably I could have bought a Samsung 830 drive, because lots of my friends told me that it is a really good drive :), actually my decision was based on the fact that my preferred hardware vendor have no Samsung disk available, so I decided to take the Vertex4.

Gian Maria

The real price of hardware

I bought a Vertex 3 240GB SSD drive for 270€ VAT included and some of my friend told that this is an expensive drive and they do not want to spend so much money for a Drive. The problem is how you use your hardware, in my life I work as a software consultant, and I spent most of the time in front of a computer compiling and programming and if spending 270€ can make my work more productive it worth the money I spent, because I can work faster.

The main reason that makes me bough a new SSD is that I work a lot with virtual machine and the difference of performance of a VM machine when run from a SSD or from my RAID of 2 velociraptor was outragous, but with my single 120 GB SSD I have trouble to make enough room to run my VM so I decided to buy a new drive. When it was time to decide what to buy I opted for a 240 GB SSD, so I could remove the RAID, all the fan dedicated to the two velociraptor (they are really hot :)) but to be honest I did not expect a great increase in overall performances. But I was wrong.

Just to give you some number, before installing the Vertex 3 drive, I took a big project of one of my customer, that has a Continuous Integration build script in MSBuild+NANT that does lots of stuff, I launched it a couple of time, and I got 132 sec the first run and 117 sec the second run (due to cache of filesystem)

Today I launch the script on the Vertex 3 drive and got 73 sec in the first run and 68 sec in the second run, this means that with my new SSD build time is really faster and I really feel my Visual Studio quicker on compilation. When you move from a standard disk to SSD you really feel different, but I assure you that you can have a similar sensation when you move from an old generation SSD to a new generation one, my Vertex 3 really outperform my old Intel X-25M.

Reading these results makes me feel that I spent my money for a good reason.

Gian Maria.

Pay attention where you attach your SSD Driver

I blogged a couple of days ago about my new Vertex3 SSD Disk, and I gave a screenshot of the CrystalDiskmark result, that I report here for the sake of discussion.

Yesterday I decided to work on my laptop while I did a fresh windows 7 install on the new disk, then I installed everything and finally re-run Crystal Diskmark again…. and I got a really different result. I did not take a screenshot, but basically I got a 350MB/sec sequential read and and an awful 150 MB/Sec on write 4K QD32, that basically is one of the reason why I choose Vertex 3 disk. I started to think what could happened, and I did a deep optimization of the system (disabling prefetch, bla bla, but the results where the same)

Then I run the test against my old intel disk, to verify if even the other disk suffer from the same loss of performance, first of all I got the old result from my blog.

If the old disk still performs at the same speed, something weird happened to my vertex 3 disk during the installation, but with my great surprise here is the results.


WHAT???? Actually my old drive is performing better then before with a good gain on the Random 4K stats. I was puzzled but I started to think to everything I did to install the new drive. Basically what I did was removing a RAID of two velociraptor and reorganizing the cables of my workstation, so I reopened it and compared the situation with a picture I took before the installation of Vertex 3. What I saw is that I swapped the SATA cable of the two SSD, nothing else, so I grab the Motherboard manual and verify each connection and found that I attached the old intel SSD disk to the Intel 6gb/sec controller and the vertex to the Marvel 6Gb/sec controller. I decided to use both controller lots of time ago, because I read in some blog that using both controller avoid saturation of the SATA if you start to heavily use both disks (I got a 2 Terabyte disk where I stored virtual machines attached to the intel controller and the intel SSD on the marvel controller), but doing a quick search in the internet I found that lots of people blame Marvel controller to have poor performances respect Intel’s one, so I finally found the reason for my Vertex 3 performance decrese, you are to blame Marvel controller"!!! Shame on you.

I attached both disk to intel controller and redo benchmarks and I obtained the same result as the day before, my Vertex 3 now is able to run at full speed :)

Modern motherboard are really complex, my P8P67 has three USB controller, three SATA Controller, etc and you need to pay attention to a lot of stuff if you want to take max performance from your hardware.

Gian Maria.