Feeds

Flash array start-up SolidFire begins the hard sell

'Virtualising performance'... with IOPS to spare

Top 5 reasons to deploy VMware with Tegile

Flash array startup SolidFire says it virtualises performance. What does it mean?

At a press briefing in Arista's offices (yes, Arista), we learnt that SolidFire offers an all-flash array with in-line deduplication, compression and thin provisioning to effectively increase the capacity and lower the cost/GB of its product versus traditional SAN arrays.

Marketing veep Jay Prassl says SolidFire offers SAN block access at cloud scale, and guarantees storage IOPS performance to thousands of volumes in one infrastructure. You can dial performance up or down separately from capacity, and specify three IOPS numbers per application: minimum, maximum and burst mode.

The maximum IOPS number is what the customer is delivered – say 500 – an IOPS being any read or write array access. The minimum is how low the IOPS rate can go if the array is very busy, say 100, and getting overloaded. For the time spent below its maximum number the customer builds up credits which can be "spent" to pay for burst IOPS, the level above, logically above, the maximum level, it not being, literally, the maximum level. A better term would be standard level.

These performance SLAs (Service Level Agreements) are based on SolidFire using Intel SSDs. A look at these reveals an apparent performance gap, with IOPS left on the table.

A SolidFire node has ten 300GB SSDs. A quick look at reference material suggests this is an Intel 320, which Prassl confirms. An Intel 320 can do 23,000 write IOPS and 39,500 read IOPS, so 10 of them should do between 230,000 and 395,000 IOPS. But a SolidFire node only does 50,000 IOPS. Why? It's as if 190,000 to 345,000 IOPS have gone missing. Why is that?

CEO Dave Wright said: "We're running mixed read/write workloads [and] our replication means the write IOPS are doubled. We set aside an IOPS allowance for rebuilds in background plus other internal stuff. So the 50,000 IOPS is the delivered IOPS to customers." In other words, the SolidFire SSDs are running faster than the 50,000 IOPS made available for customers' I/O, and this is a conservative number anyway, meaning SolidFire has performance headroom, which is reassuring.

SolidFire offers guaranteed IOPS levels, something that can be readily metered and billed for by cloud service providers, and so the array is instrumented in like a car's speedometer; pretty nifty.

It seems to us that there is an opportunity for SolidFIre to use faster single level cell flash if it wanted to push the performance envelope higher. But it gets cost advantages from using multi-level cell NAND. It tries to sequentialise writes and so reduce write amplification and extend flash' working life. Prassl confirmed that SolidFIre engineers are looking with interest at 3-bit multi-level cell flash which, if the working life was satisfactory, would enable them to raise capacity and/or to lower cost.

He pointed out that SolidFire deduplication is global, working across all volumes, whereas "NetApp ASIS only dedupes on a per-volume basis in an array and not across volumes in an array." Alex McDonald from NetApp's office of the CTO confirmed this but said NetApp can have many, many LUNS in a volume.

Prassl wouldn't supply cost/GB numbers for SolidFire but said its prices would be the same as or less than traditional SAN arrays from mainstream SAN vendors like EMC.

He said remote replication was likely coming in Q3 of 2012. General availability of SolidFire is scheduled for the second 2012 quarter, with the product currently being tested in an early access program. There is some 500TB of capacity under evaluation in this program.

SolidFire is focused pretty exclusively on cloud service providers and has good, capable software for them. TMS, Violin, and others could perhaps blow them out of the water in performance/node terms but they have no Cloud service provider-focused software, and that, Prassl said, is crucial for SolidFire's customers.

It seems to El Reg that SolidFire could possibly store bulk (nearline-ish) data on disk and tier it to flash. If the write levels get too high then SSD quality could be upgraded to enterprise-grade MLC. But this is a start-up close to product GA, and it is focusing like a laser on its markets and getting reliable and robust product out. Extending its capabilities is for the future. We speculate by the way, that SolidFire and Arista will co-operate to offer an Arista low-latency switch and SolidFire array bundle to cloud service providers. ®

Beginner's guide to SSL certificates

More from The Register

next story
Ellison: Sparc M7 is Oracle's most important silicon EVER
'Acceleration engines' key to performance, security, Larry says
Oracle SHELLSHOCKER - data titan lists unpatchables
Database kingpin lists 32 products that can't be patched (yet) as GNU fixes second vuln
Lenovo to finish $2.1bn IBM x86 server gobble in October
A lighter snack than expected – but what's a few $100m between friends, eh?
Ello? ello? ello?: Facebook challenger in DDoS KNOCKOUT
Gets back up again after half an hour though
Hey, what's a STORAGE company doing working on Internet-of-Cars?
Boo - it's not a terabyte car, it's just predictive maintenance and that
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.