Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@reed.com>
To: David Lang <david@lang.hm>,Michael Richardson <mcr@sandelman.ca>
Cc: Rick Jones <rick.jones2@hp.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat]	 Dave Täht quoted in the ACLU blog
Date: Sat, 28 Jun 2014 00:06:11 -0400	[thread overview]
Message-ID: <8aeaf238-4612-410e-8d07-38159873ea17@reed.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406271808420.17284@nftneq.ynat.uz>

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

Maybe I am misunderstanding something... it just took my Mac book Pro doing an rsync to copy a TB of data from a small NAS  at work yesterday to get about 700 Gb/sec on a GigE office network for hours yesterday.

I had to do that in our Santana Clara office rather than from home outside Boston, which is where I work 90% of the time.

That's one little computer and one user...

What does my Mac Book Pro draw doing that? 80 Watts?

On Jun 27, 2014, David Lang <david@lang.hm> wrote:
>On Tue, 24 Jun 2014, Michael Richardson wrote:
>
>> Rick Jones <rick.jones2@hp.com> wrote:
>>    > Perhaps, but where does having gigabit fibre to a business imply
>the business
>>    > has the space, power, and cooling to host all the servers it
>might need/wish
>>    > to have?
>>
>> That's a secondary decision.
>> Given roof space, solar panels and/or snow-outside, maybe the answer
>is that
>> I regularly have 2 our of 3 of those available in a decentralized
>way.
>
>given the amount of processing capacity that you can get today in a
>pasively 
>cooled system, you can do quite a bit of serving from a small amount of
>space 
>and power.
>
>The days when it took rooms of Sun boxes to saturate a Gb line are long
>gone, 
>you can do that with just a handful of machines.
>
>David Lang
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- Sent from my Android device with K-@ Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2667 bytes --]

  reply	other threads:[~2014-06-28  4:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:51 [Cerowrt-devel] " Rich Brown
2014-06-24 19:29 ` Dave Taht
2014-06-24 19:36   ` [Cerowrt-devel] [Bloat] " Steinar H. Gunderson
2014-06-24 19:45   ` [Cerowrt-devel] " Dave Taht
2014-06-24 20:01     ` [Cerowrt-devel] [Bloat] " Rick Jones
2014-06-24 20:08       ` Dave Taht
2014-06-24 21:48         ` Dave Taht
2014-06-24 21:38       ` Michael Richardson
2014-06-28  1:10         ` David Lang
2014-06-28  4:06           ` David P. Reed [this message]
2014-06-28  4:28             ` Dave Taht
2014-06-28 16:16               ` [Cerowrt-devel] Low Power UPSes (Was: Re: [Bloat] Dave Täht quoted in the ACLU blog) Joseph Swick
2014-06-30  3:45                 ` David Lang
2014-06-30 12:00                   ` dpreed
2014-06-28 16:49               ` [Cerowrt-devel] [Bloat] Dave Täht quoted in the ACLU blog Theodore Ts'o

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=8aeaf238-4612-410e-8d07-38159873ea17@reed.com \
    --to=dpreed@reed.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --cc=mcr@sandelman.ca \
    --cc=rick.jones2@hp.com \
    /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