Commentary

Howard Marks
 

Storwize Boosts Compression Appliances

All the attention that storage punditry, including this humble reporter, has given data deduplication in the past few years has pushed that old, reliable data-reduction technology compression toward the dust bin of used up technology in the minds of many storage users. That's too bad, as loss-less compression is still an important data-reduction tool. One vendor, Storwize, has made a nice little business for itself making NAS compression appliances and now it's claiming each appliance can handle 600 MB/s of traffic and archive 15:1 compression.

All the attention that storage punditry, including this humble reporter, has given data deduplication in the past few years has pushed that old, reliable data-reduction technology compression toward the dust bin of used up technology in the minds of many storage users. That's too bad, as loss-less compression is still an important data-reduction tool. One vendor, Storwize, has made a nice little business for itself making NAS compression appliances and now it's claiming each appliance can handle 600 MB/s of traffic and archive 15:1 compression.The StoreWize appliances sit in your network between the users and file based storage. User machine speak standard CIFS or NFS to the appliance which compresses the data and then speaks standard CIFS or NFS to your NAS. No client or NAS server side software is required everything happens in the black box and the data on your NSA is compressed.

Of course that means the data needs to be decompressed to be read so if you try to access the data on the NAS directly, or your Storwize appliances bights the dust, you'll see all the right file names but the contents will be compressed gibberish. Storwize will be glad to sell you a second appliance so you can make a fault tolerant cluster which will solve the problem for production environments. They also have a client decompressor for the truly paranoid like me that worry about what happens when their vendors go belly up.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I'm having a bit of trouble wrapping my head around the 15:1 data reduction claim and the fact that they use the same standard LZ type compression algorithms that never quite lived up to tape drive vendors claims of 2:1 compression. Hopefully I'll get a box in the lab to play with and prove the point.

I don't have any concerns about performance. Compressing the data reduces disk I/O, and network I/O between the NAS and Storwize but not between the Storwize and user as the data's decompressed by then, fewer disk seeks means faster performance even if the compression appliance does add a small bit of latency.

Storwize's compression is applicable to production file systems as well as backup stores and is an especially good fit with NetApp's deduping technology which doesn't do compression.

The question is with CPU cycles to spare why don't NASes compress data? Windows can and I've usually seen performance boosts on Windows file servers when NTFS compression is turned on.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links