|SolidFire gets another
$82 million funding|
|Editor:- October 7, 2014 - SolidFire today
it has closed an $82 million Series D round of funding, bringing its total
funding to $150 million. |
New investor Greenspring Associates led the
round along with a major sovereign wealth fund, with participation from current
investors NEA, Novak Biddle, Samsung Ventures and Valhalla Partners. SolidFire
will use the additional funds to extend its global reach.
building blocks of SolidFire's SSD systems are 1U
iSCSI rackmount SSDs
which include 10x 2.5"
SSDs. At that level it's the same as 100 or so other competing systems.
If you want fibre
channel access - you add a special 1U adapter rack to the native IP array.
So it's expensive - but keeps the unit costs of the most common building blocks
down - compared to including native unified storage in each rack. So in the case
of a big installation - it's a reasonable cost optimization tradeoff.
key difference is
software architecture and the fact they use a
architecture type of RAID
- which they call "no-RAID".
In SolidFire's no-RAID (which
is really big RAID) - the data is more widely dispersed across the drive
population than in classical (small architecture) RAID.
is much less disruption to data access and
performance when a drive
because SolidFire's software can manage upto about 100 racks as a raw storage
resource (1,000 SSD drives) - so the impact of a single drive down is small.
Users also have a high degree of flexibility as to how they micro manage
different virtualized segments of storage to meet their different QoS goals.
|How big was the
thinking in this SSD's design?|
|Does size really does matter in SSD
By that I mean how big was the mental map? - not how many
inches wide is the SSD. When it comes to SSDs - Big versus Small SSD
architecture - is something which was in the designer's mind. Even if they
didn't think about it that way at the time.
||For designers, integrators,
end users and investors alike - understanding what follows from these simple
choices predicts a lot of important consequences. ...read the article|
|SolidFire - as an
anti-jitter service in the cloud |
|Editor:- August 19, 2013 - SolidFire provides
the underlying rackmount
SSD support for a new SSD
empowered cloud product
Platform as a Service
(PaaS) being offered by
Solutions Now which I learned about in a
Ghaswalla on Software
Editor's comments:- cloud companies - like
the stars in the sky - are nearly numberless - however if you want to see a
partial list of who they are - SolidFire's
news page is cluttered with the names of cloud companies - and reads
almost like a set of audited customer accounts than a technology news
forum - which can be off-putting - if like me - you're looking for
SSD content -
rather than SSD
But although I couldn't find any mention of this
particular story on my brief visit to their website this time around - I was
reminded about an interesting observation which SolidFire had
about earlier (in February 2013) regarding the performance and QoS
impacts that "Noisy Neighbors" can create in a shared storage
Their leading theme is cloud service providers - but
this issue is also critical to almost any realistic deployments in an
enterprise context - and is the implicit reason that many architects have
preferred to isolate critical apps servers in the past - even within their own
datacenters - rather than risk mixing them all up in pools.
a cartoon (they call it an "infographic") -
Noisy Neighbors in the Cloud (pdf) -
SolidFire captures the essence of this performance randomizing problem - whose
solution (you guessed it) is to use more (of their) SSDs.
and SSDs, can you
trust SSD performance benchmarks?,