Featured Articles

Intel refreshes CPU roadmap

Intel refreshes CPU roadmap

Intel has revealed an update to its CPU roadmap and some things have changed in 2015 and beyond. Let’s start with the…

More...
Hands on: Nvidia Shield Tablet with Android 5.0

Hands on: Nvidia Shield Tablet with Android 5.0

We broke the news of Nvidia's ambitious gaming tablet plans back in May and now the Shield tablet got a bit…

More...
Nokia N1 Android tablet ships in Q1 2015

Nokia N1 Android tablet ships in Q1 2015

Nokia has announced its first Android tablet and when we say Nokia, we don’t mean Microsoft. The Nokia N1 was designed…

More...
Marvell launches octa-core 64-bit PXA1936

Marvell launches octa-core 64-bit PXA1936

Marvell is better known for its storage controllers, but the company doesn’t want to give up on the smartphone and…

More...
Nvidia GTX 970 SLI tested

Nvidia GTX 970 SLI tested

Nvidia recently released two new graphics cards based on its latest Maxwell GPU architecture, with exceptional performance-per-watt. The Geforce GTX 970…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 09 July 2010 08:12

OCZ Vertex 2 reviewed - 8. Iometer

Written by Sanjin Rados
thumbrecommended08_75

Review: Sandforce SF 1200 based

Iometer

Iometer was made by Intel back in 1998 as an I/O subsystem measurement and characterization tool for single and clustered systems, but is open source as of 2001 and is considered a standard benchmark. It’s used for benchmarking SSDs as well, but whether it shows actual, real-life performance is debatable.

We moved on to key tests with varying queue depths, simulating Workstation and Database operation. Queue depth in simple terms means how many commands are stacked on the SSD in a given period of time. This determines how much IO the OS (or application) will ‘allow’ the underlying controller to optimize.  By re-ordering and combining commands, physical IO can be streamlined or reduced by the controller.  The more commands the controller can process in this way before needing to report something back to the OS, the better the ’hit-rate’ of such optimizations (and hence the higher the ultimate throughput), but the trade-off is latency, which can have a devastating impact on the user experience.

It’s important to note that we’ve configured access specifications (Align I/Os on) to 4KB.

Workstation_spec2

workstation2_vertex2

workstation_transaction_time_vertex22


database

IometerDatabaseSimul

IometerDatabaseSimuTime

We tested 4K write with QD 21 as well, where Vertex 2 should, according to the specs, score about 50000. We managed 47000, which is a fascinating result.

Iometer4K

(Page 8 of 9)
Last modified on Sunday, 11 July 2010 15:58
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments