« Vendor Blogging for Dummies | Main | Cisco sneaks into the corporate laptop/desktop market with CIUS »

June 30, 2010


Feed You can follow this conversation by subscribing to the comment feed for this post.

Robert Weilheim

Animation is broke...

marc farley

Must be on your end. Its flash, streaming from YouTube. If you have a slow connection it will pause periodically.


Can you tell me the major differences between your 3PAR architecture and IBM XIV? In some way you are the same. I do not understand the reason behind your RAID. If you cut all data into chucklets why you border assembling them into RAID? IBM XIV do not do this part and can still provide lots of IO right if SATA.

marc farley

RAID is necessary for disk redundancy - which we manage at the sub-disk level with chunklets. 3PAR allows many different RAID levels concurrently to fit many different application requirements. XIV has only RAID 10, so its I/O specs are good (for SATA) but not great and also space utilization is sub-optimal. XIV only has SATA disks, which have far less IOPS than FC disks. It attempts to be a one-size fits all design, which doesn't really cut it for real-world scenarios.

3PAR Inserv arrays are multi-disk, multi-RAID so customers can create storage environments that fit a full range of requirements.


Thanks Marc. I will read more about your architecture. I know your architecture sound more appropriate for various workload. That is typically SAN are for anyway. No SAN, even NAS today, are used for one type of IO stream at the time. With hundreds of severs hammering the disks nothing is sequential anymore. It never been in my book since mainframe time too. Everything is highly random on disk ever.

Only single user access "might" think it is sequential...in fact it is not.

The comments to this entry are closed.

Search StorageRap


Latest tweets


  • Loading...


Infosmack Podcasts

Virtumania Podcasts