Advanced

Comment of the Day - October 25, 2005 Calculate the Optimal Size of a New Disk Drive

Posted by tadelste on Oct 25, 2005 10:01 PM · 4 comments
LXer -Article; By Bjorn Stadil

In answering a question on the Linux metaforum here at Lxer, bstadil wrote a splendid comment about how to figure out the optimial size of a new disk drive. He wrote: the optimal replacement size of a disk drive is e = 2.7 times what you have.

Related to: http://lxer.com/module/forums/t/18462/">Why do people switch to Linux

You asked about how I figured out the optimal size of a new disk drive?

You don't need to worry about cache size and the like. At any given time the disk drives performance is within a very narrow band. Without going into details it is because at the less performant end you can not substitute slowness for sufficient cost savings .It has been tried a few times but with little success. At the high performance end the component cost rises dramatically and the cost of drivers accordingly leaving this to various niches. The disk market is performance wise very homogeneous.

This leaves the size of your new disk as the only real decision parameter you have. Furthermore cost / GB is almost constant over the range of the sizes. If you think otherwise look at Pricewatch.com at check yourselves.

Here comes the complex part. Think about your investment in a disk drive as a cycle that keeps repeating.

Your drive gets full and you need to buy a new one. The only decision parameter you have is what size,. namely S



Each cycle is identical because I assumed that the storage growth rate is equal to the technology driven price decline of storage. (Moores law etc)

This is an excellent assumption if you think it through, and you can look at historical trends etc. What I mean by thinking it through is that most of the increase in storage needs is outside driven as we discussed. (This goes for companies and institutions as well)
You start to encode mp3's at higher bitrate as storage prices falls, Video etc. Most importantly for this assumption to hold is that there is a feedback loop. If storage cost gets ahead of the curve ie being cheaper than expected we change our behavior. Same if it falls behind.

With storage cost decline = storage requirement growth, the drive St (t is any given time) will always cost the same. The one you buy next time at optimum size S will always be the same dollar amount as the one you bought last time. The increase in S is offset by the decline of C, Both S and C should have a little subscript t like this St and Ct.

Obvious if the assumption does not hold and storage increases higher or lower than prices declines this shifts the optimal S = e, but not very dramatic and you can adjust for it but the math gets quite complicated.

An obvious thing to understand and articulate is the two forces that pulls in opposite the directions thereby creating a cost minimum. For the disk drives it is the cost of unused space and the decline of cost of storage plus scrapping of drive. Very large drive and the cost of unused space is very high, very small drive and the cost of ditching the drive is high as you amortize the cost over a short period.




Here is the Math:
**
s = Renewal size relative to current capacity
g = storage growth / time unit
c = cost / storage unit
n = Life of unit
How many time periods n does it take before your new drive of s is full?



s = (1 + g) ^ n ==> n = ln(s) / ln ( 1 + g) I omitted the size of the initial drive on both sides of initial equation., but you can put a 1 or 100.

We do not know what the cost is but we need to optimize by finding s so we have minimal cost per time period

Cost / Time Unit = ( s * c ) / n Substitute n from above and find the local minimum

Minimize { (s * c) * ln( 1+g)} / ln (s) ==> K * s/ln(s) K= Constant and disappears, presto
Minimize s/ln(s) ==> s = e



Presto Disk drive should be 2.7 times the one you have at the point where you want to replace it.

It is a little hard to read as I can't use math notation here, but hope you got the gist of it.

Return to the LXer Features

Comments (4)

ultimate in geekiness!

When I need new hard drives, I calculate thusly:

"one, two, three, many many many gigabytes."

Nice work, Bjorn!
This is not as geeky as you might think. The US storage market was $8.8B in 2004 and my little formula equates equally to $1M storage systems as it does to $100 disks.

For corporations a model like this makes it obvious that cost control needs to address what you are going to store not what you already have. What outside forces are driving the storage needs and what different classes of needs are at play with different requirement and cost / GB.

The likes of EMC, SUN (the bought Storage tech for some odd reasons) and Hitachi should think about how to strategically use these kind of models in their marketing and positioning efforts. .Even open source can benefit from this as at least Redhat has discovered. Target some of the lower requirement, high growth classes of storage needs and present a clear model for cost containment and Bobs your uncle.
for a Corporate model this makes sense. For my personal use, I'll go pretty much the tuxchick route... 3 to 5 x my current space will work fine, depending on my current financial state.

This looks like rocket science

IIRC the rocket equation for a multi-stage rocket looked vaguely similar... a stage will achieve the same end velocity as its outgoing gas stream if the mass ratio fully tanked/empty is e :-)

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post

LXer

  Latest Features
bob: LXer now speaks Markdown
Oct 27, 2026

bob: How to protect against PHP2Shell
Oct 26, 2026

Scott Ruecker (San Diego, U.S.): Linux That's Small
Oct 14, 2024

penguinist: Encryption, Trust, and the Hidden Dangers of Vendor-Controlled Data
Aug 27, 2024

Scott Ruecker (San Diego, U.S.): My Linux Mint Tribute
Aug 23, 2024

Scott Ruecker (San Diego, U.S.): How I Turned My Chromebook Into A "Mintbook"
Jul 08, 2024

Scott Ruecker (San Diego, U.S.): Adventures With My New Chromebook
Jun 10, 2024

Scott Ruecker: My Linux Laptop
May 08, 2022

Scott Ruecker: Laptop Dual Boot Project: Part 2
Nov 30, 2021

Scott Ruecker: Laptop Dual Boot Project
Nov 30, 2020


View all

  Search Features

Search LXer Features:

[ Copyright © LXer | All times are recorded in Central Daylight Time (CDT) ]

[ Contact Us | Privacy Policy | Terms of Service | About us | rss | Mobile ]

Login