Comments on: IBM tests 4-terabyte solid-state drive tech
Big Blue announces solid-state drive technology that achieves high speed and power savings, even if only in the labs so far.
Big Blue announces solid-state drive technology that achieves high speed and power savings, even if only in the labs so far.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
Brooke Crothers has served as an editor at large at CNET News, an editor at Dow Jones' Asian Wall Street Journal Weekly, and a senior editor at InfoWorld. His CNET blog covers chip technology and computer systems, and how they define the computing experience. He also contributes to The New York Times' Bits and Technology sections. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.
Add this feed to your online news reader
Either way, I'd say somewhere in the upper 5th if not 6th figure area.
How would Fusion's ioDrives fit in IBM's storage? I thought they were SSDs made for servers?
The workload benchmarked was 70/30 4K all miss which is somewhat representative of a typical database workload.
If people have actually played with SSD devices, they will know that the claimed X0,000 reads and Y,000 writes are all very well when doing 100% read or write at say 512 byte transfers, but bump up the transfer size, and throw in a mixed workload and you will prune the men from the boys... i.e. IOPs will be no where near those claimed by manufactures...
While EMC has been shipping SSDs since the 2Q, the question I'd ask is how many DMX quadrants would be needed to provide this same level of IOPs... many many... which defeats the power and spaces savings that SSDs can provide.
Anyone interested in more details of what we have been doing see my recent blog post :
http://www.ibm.com/developerworks/blogs/page/storagevirtualization?entry=1m_iops_from_flash_actions
For write workloads, storage controllers have added cache and the like to hide such latency, but that becomes less improtant with flash. Also consider a (large) FC-AL loop of HDD, say 128 HDD, then the dual loop config needs to only support say 128x350 IOPs ~=45K iops (assuming all HDD are flat out - which is unlikely to be possible) so thats one flash device... There are likely to be bottlenecks further up the system too... So while it does help improve latency by using existing controller devices, it cannot max out the devices, not can it provide the best latency.
With a modular system like IBM SVC, then you have 50us of latency top to bottom of the stack, and with the flash devices typically giving 400us under heavy load, you can keep to around 700us for the entire system, host -> SAN -> SVC -> flash.
Monolithic controllers are fine until they reach their limit, then you need to bring in another monolith and scale out in islands, with a modular scale out box, you simply add more processing nodes (SVC) to the cluster, and more storage behind the cluster and still have a single image and control point.
For this config we used around 40 FusionIO cards.
Was this testing also done with some form of data protection?
- by bitbucketio September 10, 2008 10:16 AM PDT
- orbist : I assume you're using the IOdrive without the IOsan port. How many IOdrives were in your test?
- Like this Reply to this comment
-
(14 Comments)Are there any plans to use the IOsan in your storage solutions independent of the SVC?
http://www.fusionio.com/PressDetails.aspx?id=44