« EMC’s Decho and the Long Arm of the Law | Main | ABC and Storage Costs (Part 1) »

November 20, 2008

Comments

Couldn't agree more. As a matter of fact, I'd extend that thought to data deduplication and other areas :-)

As far as modelling costs for spin-down, for some time now, EMC has offered a power calculator that's very popular with our customers. We already owned a vast array of EMC and non-EMC arrays, servers, switches, etc.

Rather than just go by spec sheets, we measured actual power draw at light, medium and heavy loads. We also did field measurements of what people pay for power, cooling, etc. since those numbers are not always on hand.

So, when we model cost-savings for spin-down, it's pretty easy to look at the delta between power draws, approximate power-on vs. power-off duty cycles, apply either the actual or estimated costs for power and cooling, and arrive at a pretty realistic number "here's what it's worth" without too much drama.

Not everyone can see cost savings -- true.

But many can, and being able to get to that number ahead of time -- using customer's actual data -- helps to justify the feature.

I think the tool has become most of our popular, simply because it uses actual measure power draw numbers, and covers all manner of data center equipment including EMC's. The power/cooling cost survey is pretty popular as well.

So, have you guys done anything to create a real-world power calculator that you can put in customers' hands?

Cheers!

Wow, that was quick. You have some form of hyperdrive keyboard attached to a time machine version of VMware on your laptop? Or are you reading my posts as I type them? Must check for spyware....

You make a good point about power calculators, but that's a fractional part of what I mean, and it highlights the problem.

Let's say your power calculator states that I'll save $3000/year by using spindown 23 hours out of 24.

Great! Let's do it.

But wait a moment; to utilise spindown, I need to have some form of data management strategy that lets me take advantage of it. I need to analyse my data & identify suitability for this treatment (cost), change processes (cost), move my data (cost), retrieve it when required (cost), transfer it to other media in the medium/long term as technology gets replaced (cost) etc etc.

For backup & archive, that's probably a little easier than most to assess, but only marginally, and it's only part of the lifecycle of data cost.

For first generation data right through to archive, it's not that easy -- or cheap to do. An example that springs to mind was your "suggestion" that NetApp should spindown some of its data based on research we'd done on access patterns, size and age of data we store in a CIFS environment. Apparently, we could save a shedload of money that way.

I don't think so. That's where a whole life cost model of data is needed, and an understanding of how it's used, frequency of access, cost of storage and so on.

Once we've done the analysis (cost), changed process (cost), moved data through tiers (cost), retrieved it when required (cost), transfered it to other media in the medium/long term as technology gets replaced (cost) and so on, our $3000/year saving may be not a saving at all.

What does it really cost to do something, as opposed to what I'd save by doing nothing? Having a power calculator doesn't answer that.

Many years ago in a galaxy far away I and some colleagues worked to develop a product to build ABC (Activity Based Costing) models for IT. I found some interesting models for digital document management in library management systems this afternoon that reminded me of them. I think I'll explore further.

As to dedupe, that's a part of the data management story. Right now, with disks still spinning beause no-one can take advantgage of spindown on primary, it's a big save, because it has such small marginal costs.

Unless, of course, it's not available. Or free :-)

Alex and Chuck,

I agree that there aren't currently any big economic gains from spin down, but I think Tony was writing his list with a forward-looking perspective.

Spindown lacks a critical mass of software to make it work, but I believe that it will be developed (I don't know who will do it necessarily) to address the need corporations have to store the mountains of data that sporadically needs to be accessed - and is required by laws and regs.

Spin down works very well for me with several USB and Firewire disk drives. Just this week I happily re-started an audio project of mine that needed to come back from stationary dormancy. I like the fact that this data wasn't consuming any power these many months. For me, its removable, but in the corporate world I think spin down makes a lot more sense.

The same question could be asked about flash SSDs. I don't see that much of a requirement for them today either due to their current premium pricing and the economic conditions. Of course, their application is much easier to understand, - high performance storage. But disk drives have continued to surprise for many years and other less expensive technologies, such as wide striping could limit SSDs market penetration.

If the economic malaise drags on, I give spin down better odds than flash.

Ultimately, the disks that consume the least power of all are the ones that never had to be used in the first place.

This has always been my thinking whenever COPAN would come up. Great that they can turn their disks on and off, but what have they actually done to reduce the amount of disks used in the first place?

These days it's looking more like COPAN itself has been spinning down.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

© NetApp, Inc.  |  "Safe Harbor" Statement  |  Privacy Policy