From: Andrew LeCody <andrewlecody@gmail.com>
To: Chris Williams <chris@icloudtools.net>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Date: Tue, 8 Apr 2014 12:18:01 -0500 [thread overview]
Message-ID: <CAEX2NScPaCVxN8Ec=xhcZE6D_KY5QB2LQne61=G1=QQV534HOg@mail.gmail.com> (raw)
In-Reply-To: <6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net>
[-- Attachment #1: Type: text/plain, Size: 2822 bytes --]
My node (based in Dallas, TX) has about 240 connections and is using a
little under 4 Mbps in bandwidth right now.
According the hosting provider I'm at 11.85 Mbps for this week, using 95th
percentile billing. The report from my provider includes my other servers
though.
On Mon, Apr 7, 2014 at 12:39 PM, Chris Williams <chris@icloudtools.net>wrote:
> I’m afraid this is a highly simplistic view of the costs of running a full
> node.
>
> My node consumes fantastic amounts of data traffic, which is a real cost.
>
> In the 30 days ending Apri 6, my node:
>
> * Received 36.8 gb of data
> * Sent 456.5 gb data
>
> At my geographic service location (Singapore), this cost about $90 last
> month for bandwidth alone. It would be slightly cheaper if I was hosted in
> the US of course.
>
> But anyone can understand that moving a half-terrabyte of data around in a
> month will not be cheap.
>
>
> On Apr 7, 2014, at 8:53 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>
> > On Mon, Apr 7, 2014 at 8:45 AM, Justus Ranvier <justusranvier@gmail.com>
> wrote:
> >> 1. The resource requirements of a full node are moving beyond the
> >> capabilities of casual users. This isn't inherently a problem - after
> >> all most people don't grow their own food, tailor their own clothes, or
> >> keep blacksmith tools handy in to forge their own horseshoes either.
> >
> > Right now running a full node consumes about $1 in disk space
> > non-reoccurring and costs a couple cents in power per month.
> >
> > This isn't to say things are all ducky. But if you're going to say the
> > resource requirements are beyond the capabilities of casual users I'm
> > afraid I'm going to have to say: citation needed.
> >
> >
> ------------------------------------------------------------------------------
> > Put Bad Developers to Shame
> > Dominate Development with Jenkins Continuous Integration
> > Continuously Automate Build, Test & Deployment
> > Start a new project now. Try Jenkins in the cloud.
> > http://p.sf.net/sfu/13600_Cloudbees_APR
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3939 bytes --]
next prev parent reply other threads:[~2014-04-08 17:18 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:34 [Bitcoin-development] Why are we bleeding nodes? Mike Hearn
2014-04-07 12:17 ` Ricardo Filipe
2014-04-07 13:43 ` Andreas Schildbach
2014-04-07 14:05 ` Mike Hearn
2014-04-07 14:15 ` Eric Martindale
2014-04-07 14:23 ` Mike Hearn
2014-04-07 19:46 ` Troy Benjegerdes
2014-04-08 3:13 ` kjj
2014-04-08 7:50 ` Mike Hearn
2014-04-09 10:38 ` Wendell
2014-04-09 11:15 ` Wladimir
2014-04-07 14:45 ` Tom Harding
2014-04-07 12:19 ` Jameson Lopp
2014-04-07 12:26 ` Pieter Wuille
2014-04-07 12:34 ` Mike Hearn
2014-04-07 12:34 ` Jameson Lopp
2014-05-20 18:38 ` Isidor Zeuner
2014-04-07 13:50 ` Gregory Maxwell
2014-04-07 13:53 ` Gregory Maxwell
2014-04-07 13:58 ` Jameson Lopp
2014-04-07 14:04 ` Gregory Maxwell
2014-04-08 11:28 ` Jesus Cea
2014-04-07 15:45 ` Justus Ranvier
2014-04-07 15:53 ` Gregory Maxwell
2014-04-07 16:02 ` Jameson Lopp
2014-04-07 16:27 ` Mark Friedenbach
2014-04-07 16:57 ` Gregory Maxwell
2014-04-07 17:01 ` Mark Friedenbach
2014-04-07 17:16 ` Gregory Maxwell
2014-04-07 17:35 ` Brent Shambaugh
2014-04-07 17:40 ` Mike Hearn
2014-04-07 17:44 ` Gregory Maxwell
2014-04-07 17:45 ` Tamas Blummer
2014-04-07 17:50 ` Justus Ranvier
2014-04-07 18:30 ` Arne Brutschy
2014-04-07 17:56 ` Brent Shambaugh
2014-04-07 17:46 ` Justus Ranvier
2014-04-07 17:39 ` Chris Williams
2014-04-07 18:23 ` Mike Hearn
2014-04-07 18:35 ` Tamas Blummer
2014-04-07 18:49 ` Gregory Maxwell
2014-04-07 19:00 ` Tamas Blummer
2014-04-07 18:48 ` Mark Friedenbach
2014-04-07 19:02 ` Gregory Maxwell
2014-04-07 19:05 ` Tamas Blummer
2014-04-07 19:03 ` Gregory Maxwell
2014-04-07 19:13 ` Tier Nolan
2014-04-07 19:20 ` Tamas Blummer
2014-04-07 19:13 ` Mark Friedenbach
2014-04-07 19:36 ` Tamas Blummer
2014-04-07 21:46 ` Ricardo Filipe
2014-04-07 19:30 ` Paul Lyon
2014-04-07 19:50 ` Tamas Blummer
2014-04-07 21:48 ` Tier Nolan
2014-04-07 21:56 ` Gregory Maxwell
2014-04-08 3:44 ` Jeff Garzik
2014-04-08 7:24 ` Jean-Paul Kogelman
2014-04-08 7:59 ` Tamas Blummer
2014-04-08 17:18 ` Andrew LeCody [this message]
2014-04-07 17:07 ` Drak
2014-05-20 8:15 ` bitcoingrant
2014-05-20 8:42 ` Mike Hearn
2014-05-20 14:37 ` Eugen Leitl
2014-05-20 14:52 ` Gmail
2014-05-20 18:46 ` Andy Alness
2014-05-20 19:17 ` Jeff Garzik
2014-05-20 20:09 ` Andy Alness
2014-05-20 20:22 ` Jeff Garzik
2014-04-07 21:55 Paul Lyon
2014-04-07 22:14 ` Tier Nolan
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='CAEX2NScPaCVxN8Ec=xhcZE6D_KY5QB2LQne61=G1=QQV534HOg@mail.gmail.com' \
--to=andrewlecody@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=chris@icloudtools.net \
/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