How much wood could a woodchuck chuck if a woodchuck could chuck wood? I think I care more these days about how fast I could chuck the wood than how much wood I could chuck.
With the existence of Giga-speed switches and Giga-speed NICs even in our notebooks, moving data through today’s intra-networks has become luxurious to the average computer user. And figuring that most offices now have at a minimum T-1 speed, the hazards of downloading large documents have become an after thought.
But let’s think about transfering data for a moment. Maybe electronic transfer is not as efficient as we ‘assume’ it is just because it’s become convenient and easy for us. Referencing the chart*** below to gauge the size of data I’m talking about, let’s think about moving a petabyte of data from a hosting facility, across the Internet, to a remote backup facility. Let’s make an assumption that we’re talking about T-1 connections which allow data transfer of about 1 MB per second (rounded estimates for my non-mathematical brain today). A petabyte of data equates to one billion megabytes. So quick thinking tells me that I need one billion seconds (assuming a great connection at both points and no outside interfering forces), or 16.67 million minutes, or 277.77 thousand hours, or 11.57 thousand days or 31.7 years. Wow!
Okay, okay. So who’s going to download a petabyte of data? Well believe it our not, this attempt is common. Or atleast the need to is commonplace in today’s IT world.
Let’s get back to my original question. Moving a petatbyte of data - can I drive to California (from Virginia) and back faster? Let’s map out the fastest route on Google Maps and see what Larry and Sergey and the boys say. From Norfolk, VA to San Jose, CA is 5,914 miles roundtrip equating to 88 hours of drive time or 3.67 days. Huh? Dare I say the rather absurd question that I asked may turn out to be my best option? Over our beloved technological abilities?
As a person that manages projects and budgets everyday, I’m now asking my network guy to hop in his car and drive for 3.67 days versus starting the data transfer from our servers that will take 31.7 years to complete. No brainer! Right? Or wrong?
***
Quantities of bytes
kilobyte (kB) 103 = 10001
megabyte (MB) 106 = 10002
gigabyte (GB) 109 = 10003
terabyte (TB) 1012 = 10004
petabyte (PB) 1015 = 10005
exabyte (EB) 1018 = 10006
zettabyte (ZB) 1021 = 10007
yottabyte (YB) 1024 = 10008
Tags: California, data, EB, exabyte, GB, gigabyte, kB, kilobyte, MB, megabyte, NIC, PB, petabyte, T-1, TB, terabyte, Virginia, YB, yottabyte, ZB, zettabyte