The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] History repeating itself
Date: Sat, 30 Jul 2016 15:30:36 +0000	[thread overview]
Message-ID: <20160730153036.GI3375@yeono.kjorling.se> (raw)
In-Reply-To: <20160730141537.GA12724@mercury.ccil.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2805 bytes --]

On 30 Jul 2016 10:15 -0400, from cowan at mercury.ccil.org (John Cowan):
>> Who needs FedEx?  
> 
> Well, latency counts for something too, as does radius: if I want to
> send bulk data from New York to London (a very normal thing to do),
> your station wagon isn't going to count for much.

You could, however, get an economy class flight ticket and load up
your suitcase with either HDDs or SDXCs (I suspect SDXCs would be
better per amount of data from the perspective of both volume and
weight, and would take better to handling). Given FedEx's prices,
_once you have the infrastructure set up_ (which you'll need whether
you have someone travel with the media, by air or by stationwagon, or
FedEx it), that _might_ even compare favorably in terms of bytes
transferred per second per dollar. (Now that's a measurement of
throughput I don't think I've seen before; B/s/$.) Of course, you'd
need someone who can babysit the suitcase, which potentially adds to
the cost, but the stationwagon traditionally hasn't been self-driving
either, and most of a transatlantic flight isn't active time on part
of the person travelling with the suitcase so you could go with an
overnight flight and allow the person to sleep.

If you want to reduce the risk of the bag getting handled roughly or
lost in handling, reduce the above to carry-on luggage; it will still
provide a quite respectable throughput.

If carry-on allows 10 kg (it's been quite a while since I flew
commercially) and a SDXC card that can store 200 GB weighs 5 grams
(seems a reasonable back-of-the-napkin estimate), that would allow
approximately 200 GB * 2,000 = 400 TB transferred in say ten hours
flight time, for a 40 TB/h ~ 11 GB/s (90 Gb/s) throughput,
disregarding the time to write to and read from the media (which
applies equally with a stationwagon or FedEx). If the ticket costs
$500, that's roughly 200 Mb/s per dollar (and remember, we are only
relying on carry-on here). What's more, it is relatively trivially
parallelizable at an approximately linear increase in cost, and can be
scaled according to need at each time. If you can live with the risk
of rough handling, the throughput per dollar approximately quadruples
(700-900 Mb/s/$) given a 20 kg per person maximum checked-in baggage
weight.

It might not be the absolute cheapest approach, but it seems rather
hard to beat in terms of throughput per dollar for bulk data transfer,
especially if you already have someone who would travel anyway and can
be convinced to take a company-approved suitcase in return for having
their ticket paid for.

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


  reply	other threads:[~2016-07-30 15:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 20:28 [TUHS] Unix v6 problem with /tmp Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57   ` Clem Cole
2016-07-27 21:01     ` Clem Cole
2016-07-27 21:10     ` William Pechter
2016-07-28  0:49       ` Clem cole
2016-07-28  1:03         ` William Pechter
2016-07-28 11:23           ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) Michael Kjörling
2016-07-28 12:18             ` Tony Finch
2016-07-28 13:57             ` John Cowan
2016-07-30  7:56               ` Greg 'groggy' Lehey
2016-07-30 11:41                 ` William Cheswick
2016-07-30 23:28                   ` Greg 'groggy' Lehey
2016-07-30 23:50                     ` scj
2016-08-01 11:36                   ` Tony Finch
2016-07-30 14:15                 ` John Cowan
2016-07-30 15:30                   ` Michael Kjörling [this message]
2016-07-28  1:03       ` [TUHS] Unix v6 problem with /tmp Clem cole
2016-07-28 23:16     ` [TUHS] environments/universes (was: Unix v6 problem with /tmp) Sven Mascheck
2016-07-29  3:05       ` arnold
2016-07-29 14:14         ` Clem Cole
2016-07-29 13:55       ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160730153036.GI3375@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).