Cinetica  
chi siamo soluzioni e servizi successi blog  
Articoli con tag ‘Fast Track’
CINETICABLOG

Archeology or Technology?

On friday @plankers sent this Tweet:” 2.5″ 10k disk is as fast as a 3.5″ 15K disk. Did not know that, thanks @Compellent #TechFieldDay“! yes, it sound a little bit strange and it is inaccurate but twitter’s 140 chars limit doesn’t help to fully explain the whole story.

Simply put, this result is achieved positioning most accessed data on the outer tracks of the disks but, after this Tweet, a furious quarrel started about doubts some competing vendors raised. The discussion was closed by the storage anarchist and alextangent with twitts like: “the math (& observed reality) doesn’t support the mktg BS. BTW the BEST data placement is MIDDLE of platter” and   “mid-platter data placement well understood since winchester tech 1st appeared; 1970-80s!” …. But it’s not finished yet!

Well, they tried to do some unrealistic FUD stating that Compellent’s Fast track is based on wrong concepts and it doesn’t work!

A short prologue
Compellent has a software feature called Fast Track. This features is used, with success, by many Compellent customers to get more IOPS per disk! It works and satisfied customers can confirm this.
I wrote a lot on FT in the past and you can find articles in my blog by clicking hereherehere or searching “fast track” for a full list.
You can also find a nice and illuminating video about Fast Track on the Compellent’s website.

How is it possible?
It’ simple Compellent Storage Center is a next generation storage system and was architected less then 10 years ago (not in 80s o even in 70s!).
The Compellent architecture is not comparable to old generation (i.e.: clariion or V-Max) arrays because it redefines the basic concepts about how data blocks are stored and managed!  Comparing Compellent’s storage architecture to the EMC’s arrays architecture equals to compare Technology and Archeology!

When Barry and Alex say that they get the best performance from the array positioning most accessed data blocks on the middle of the disk they speak about technologies of the last century: (winchester disks: 40 years ago!), arrays (designed on archaic raid techniques) and very old algorithms (those you’ll likely find in the base foundation of old generation arrays)… so we must admit we are speaking about archeology surely not about nowdays technology!

The options are two: These guys are biased or they ignore how Compellent works (probably both).

Fast track works because it is integrated with data progression: a true Fully Automated Storage Tiering available since years, not a feature like EMC’s FASTv2 promised more than 1.5 years ago! You can’t expect automatic data placement optimization (like fast track) from companies that can’t offer a true Automtated Tiered Storage.

In vitro Vs. real life
We have studied and tested all the Compellent software features intensively before start to sell these systems in Italy two years ago and I can say that fast track works: we have a lot of documentation on this and we achieved more than 30% improvements after having enabled it on our system.
The world is not perfect and 30%, sometimes, drops down to 20 or even 15: it depends on the number of the hosts and the applications involved but this anyway means that you can buy up to 20% less disks!

Now, if I add my 20% to a 10/12% of 2,5″ Vs. 3,5″ (improvement in IOPS due to the less latency), I get more or less 30/32% improvement. That’s why a 10K/2,5″ disks “equals” a 15K/3,5″ IOPS!

Obviously I’m not telling you a 2.5″ 10k disk is as fast as a 3.5″ 15K disk. But we can say that the fastest tracks of a 10K RPM 2,5″ disk can give you the same average IOPS a 15K RPM 3,5″ disk can offer… If you can use them the right way.

Last, but not least, Barry where do EMC arrays write the most accessed data blocks? I hope automagically in the middle of the disk! Because a Compellent’s array can decide where to put most accessed data but I’m not sure Clariions and VMaxes can!

Related Posts:

How Compellent Storage Center works – Part 1

I’ve been very busy this week, didn’t get enough time for social activities (online and offline), while I was cutting my way through some weird Solaris issues I had a chance to think about how Compellent technology is understood in the storage tech community.

And my conclusion was: not enough :-)

So, recently I had a discussion over at RecoveryMonkey.net about how Compellent technology really works, and I tried to create a comprehensive post out of that discussion.

How Compellent Storage Center works

Dynamic Block Architecture

First of all, every chunk of data on a Storage Center system is stored in what’s called a PAGE, that’s referred in Compellent’s brochure as DBA (Dynamic Block Architecture).

The concept is pretty similar to virtual memory, basically you’re abstracting from the physical disk to an entity that can live on different medium, the single PAGE defaults to 2MB of size, but it’s tunable to 512k or 4MB, you can even have different PAGE sizes on the same Disk Folder (albeit not recommended).

Every PAGE comes with an attached Metadata, this metadata stores everything related to this PAGE like:

  • When it was created
  • When it was last accessed
  • What kind of RAID protection currently has (R10, R5, R6…)
  • What kind of tier it currently lives in (Tier 1, 2 or 3)
  • What kind of disk tracks it lives in (FAST or Standard)

With this kind of data available for every PAGE in the system, Storage Center start to collect statistics on how the PAGEs are accessed, and adjust accordingly moving the PAGEs between different Disk Tracks, RAIDs and Tiers during its scheduled Data Progression.

Storage Profiles

To control HOW the Volumes are written/progressed through the system there’s a functionality called “Storage Profiles”, these Storage Profiles define what Tiers and RAID level a volume can use for Active data and Snapshot data, there are four default Storage Profiles and then the End User can create a custom one on its own (it’s a matter of a few clicks), let’s see more in deep how they works:

Tiers are organized like that:

  • 1st Tier – Fastest disks
  • 2nd Tier – Medium disks
  • 3rd Tier – Slowest disks

and they’re dynamically chosen based on the available drives in the storage, every tier is subdivided in different RAID Levels and different Tracks.

To clear things up, let’s imagine that we have a system configured with:

15 active drives FC 450GB 15K

15 active drives SATA 1TB 7.2K

With this kind of system we would have:

Tier 1 – 15K drives

  • RAID 10 Fast Tracks
  • RAID 5-9 Fast Tracks
  • RAID 10 Standard Tracks
  • RAID 5-9 Standard Tracks

Tier 3 – 7.2K drives

  • RAID 10 Fast Tracks
  • RAID 5-9 Fast Tracks
  • RAID 10 Standard Tracks
  • RAID 5-9 Standard Tracks

I’m using an “old” example since right now you can also have RAID 6 in the mix but let’s leave that alone for now, also RAID 5-9 means that it’s a RAID stripe made of 8 Data blocks and 1 Parity block (You can also have RAID 5-5 if you want)

So in this system my data can live on those 8 “tiers”, right now when I create a new Volume (LUN) I can choose where to put my active data and my snapshot data by selecting a “Storage Profile”, for example let’s use a best practice for that:

The “Recommended (All Tiers)” default profile is the most used and it’s configured with:

  • Write data on Tier1:RAID 10 and Tier2:RAID 10
  • Snapshot data on Tier1:RAID 5-9, Tier2:RAID 5-9, Tier3:RAID 5-9

I usually create another custom Storage Profile called “Archival Data (R5-9)” that’s configured with:

  • Write data on Tier3:RAID 5-9
  • Snapshot Data on Tier3:RAID 5-9

To accommodate the need for low impact stuff.

How data flows to Storage Center

Considering that let’s see how the data flow is for those two profiles:

— Profile “Recommended (All Tiers)

  • Data flow from the server HBAs to Compellent front-end ports
  • the Data stage to write cache (512MB per controller) and it’s replicated to the other controller.
  • The data is written to disk on the Tier1, Fast Tracks in RAID 10.

The data is now on stable storage.

— Profile “Archival Data (R5-9)

  • Data flow from the server HBAs to Compellent front-end ports
  • The Data stage to write cache (512MB per controller) and it’s replicated to the other controller.
  • The data is cached until a full stripe write is possible.
  • The data is written to disk on the Tier3, Fast Tracks in RAID 5-9.

The data is now on stable storage.

Data Progression

After the data is on disk there are several ways to progress to the lower tiers, if you just leave the Volume (LUN) alone, the system will continue to keep statistic for every PAGE written, and then progress it slowly (the algorithm is based on access threshold on a 14-day basis) to the lower tiers.

Instead, if you take a Replay (the terminology used by Compellent for Snapshots), either using scheduled snapshot or manually, the data progress quicker, just for example, let’s imagine we have a 100GB volume (LUN):

— it’s 12.00 pm

  • We write 10GB of data (let’s call it Data Blob 1), it’s in Raid 10 on Tier 1, Fast Tracks, and it’s consuming 20GB of raw space (100% raid overhead due to Raid10).
  • take a Replay of the volume.

— It’s 3.00 pm

  • We write another 5GB of data (call it Data Blob 2), that’s also in Raid 10 on Tier 1, Fast Tracks, 10GB of Raw Space (grand total of 30GB).

Usually at 7.00 pm (that’s the default but it’s configurable) the Data Progression Job kicks in, due to the fact that Compellent snapshots are pointer based (more on that in another post) what we’ve called “Data Blob 1 becomes a Read-Only Blob of data and it progress immediately to Raid 5-9 to get some free space back.

So the next morning we find the system in this situation:

Blob Data 1 which is now part of the Snapshot Data is written in Raid 5-9 on Tier 1, Fast Tracks, consuming almost 12 GB of Raw Disk Space

Blob Data 2 which is part of the Active Data is still written in Raid 10 on Tier 1, Fast Tracks, still consuming 10 GB of Raw Disk Space

We just got 8GB of Raw Disk Space back, without sacrificing performances, because “Blob Data 1″ is considered “Read Only” thus we don’t have to write Raid 5 but just read from it, eliminating the raid penalty.

If we’re going to write data on that volume we’ll still write to “Blob Data 2” that’s still active data, still in Raid 10.

Now, that’s all for today, in the next posts I will outline how pointer-based snapshots works on Storage Center, how Replication works and other nifty features.

Fabio Rapposelli

This post originally appeared on my blog: http://p2v.it

Related Posts:

Ecco perchè Compellent ti propone meno dischi

Sono dispiaciuto di leggere post come questi.

Probabilmente, come per sua stessa ammisione, chi scrive quel blog non conosce molto bene lo storage Compellent e magari c’è bisogno di una spiegazione per capire meglio come è possibile raggiungere certi risultati.

Vorrei dire innanzitutto che non conosco l’ambiente di questa particolare trattativa/progetto, ma sono un rivenditore Compellent e lavoro ogni giorno per configurare sistemi.

Prima di tutto noi usiamo il 99mo percentile (come suggerito da Compellent) e non il 95mo. In più consideriamo 177 IOPS e non 220 IOPS per i dischi a 15000 Giri. Utilizziamo inoltre documenti Compellent interni per fare delle configurazioni adeguate. Compellent è davvero (quasi troppo) pignola nella raccolta dei dati del cliente (iops, spazio, latenze, n. di server coinvolti, tipo di carico…etc), quindi mi sembra strano quello che hai scritto.

Compellent, diversamente da NetApp, fornisce Fast Track, Data Progression e Dynamic Block Cache, queste funzionalità aiutano ad ottenere una maggiore performance con un minore impiego di risorse rispetto ai concorrenti. Utilizzandole assieme è possibile raggiungere numeri davvero impressionanti!

Seguimi in questi calcoli: 11 dischi attivi (supponendo che un cassetto con 12 dischi ne abbia uno di spare), raggiungono circa 2000 IOPS ma:

Fast Track

è la capacità di scrivere dati sulla porzione più veloce dei dischi (tracce esterne, circa il 20% dello spazio disco) e ottenere più IOPS e meno latenza.

Se puoi scrivere/leggere dati sulle tracce esterne puoi guadagnare, in pratica, qualcosa come il 15/30% di miglioramento delle performance con una notevole diminuzione della latenza dei tuoi dischi (l’effettivo vantaggio dipende dal numero di server e dalla dispersione delle scritture).

In questo caso Il nuovo totale sarebbe di 2000+20% = 2400 IOPS. ;)

Data Progression

è l’automated tiered storage (non importa cosa tu o la tua compagnia ne pensi ma, se ben implementato, permette un notevole vantaggio). Data Progression, grazie a Fast Track, può lavorare anche su un solo tipo di dischi!

Quindi puoi scrivere dati in Raid10 sulle tracce più veloci e poi farli migrare, secondo politiche e profili, verso Raid5/6 in altre parti del disco.

Con altri produttori devi scegliere in anticipo il tipo di Raid (Raid5 o 6 per risparmiare spazio, Raid10 per avere migliori performance, ma non entrambe sullo stesso volume!).

Non aumentiamo in questo modo le IOPS ma, di sicuro, non le peggioriamo per effetto della scelta di un particolare Raid.

Dynamic Block Cache

La cache di Compellent è piccola (512MB per le scritture in mirror e 3GB a controller per le letture) ma è davvero flessibile e intelligente!

Per ogni LUN puoi scegliere il comportamento della cache e la grandezza del blocco varia dinamicamente tra 2KB e 256KB, significa che il controller alloca lo spazio necessario e non uno prefissato. Nel mondo reale significa che hai più spazio e flessibilità nel gestire i flussi I/O rispetto all’utilizzo di blocchi prefissati.

Spero di aver chiarito al meglio perchè Compellent propone meno dischi dei concorrenti nella maggior parte dei casi.

Related Posts:

     
Latestnews

Cinetica è sponsor di CLOUDscene (a Bologna il 30 settembre 2010 c/o Hotel Royal Carlton). Evento dedicato al cloud computing pubblico e privato riservato a CEO,CIO/CTO e CFO.

Se sei interessato a ricevere un invito, contattaci.

Related Posts:

  • No Related Posts
 
Perchè rivolgersi a noi
Soluzioni hardware/software complete e pienamente integrate.
Progettazione realizzazione di infrastrutture Virtualizzate.

Consulenze specializzate per l'implementazione e il mantenimeto di infrastrutture HW e SW in ambiente enterprise.

Qualità e innovazione nelle soluzioni offerte, allineate con le esigenze dei clienti.
 
Blog
Uno dei fattori di successo di cinetica è l'entusiasmo per quello che facciamo, è per questo che abbiamo deciso di pubblicare un Blog dove condividere le nostre idee e le esperienze con chi lo desidera...CONTINUA
     
         
 
CONTACT
World Trade Center (Torre B)
via Consiglio dei sessanta, 99 Dogana
47891 Repubblica di San Marino (RSM)
  +39 0549 908 096  |  +39 0549 908 054
 
 
RSS Articoli | RSS Commenti
Copyright © 2009 Cinetica. All Rights Reserved.

site design: openspace soluzioni creative
powered by WordPress