From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QpRyu-0003DU-8r for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 21:31:00 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me designates 173.246.101.161 as permitted sender) client-ip=173.246.101.161; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QpRyt-00072B-El for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 21:31:00 +0000 Received: from [IPv6:2001:470:9ff2:1:ee55:f9ff:fec6:e666] (unknown [IPv6:2001:470:9ff2:1:ee55:f9ff:fec6:e666]) by mail.bluematt.me (Postfix) with ESMTPSA id 107832563 for ; Fri, 5 Aug 2011 23:30:48 +0200 (CEST) From: Matt Corallo To: Andy Parkins In-Reply-To: <201108051403.05506.andyparkins@gmail.com> References: <201108041423.14176.andyparkins@gmail.com> <201108051258.25813.andyparkins@gmail.com> <1312545969.4516.8.camel@BMThinkPad.lan.bluematt.me> <201108051403.05506.andyparkins@gmail.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-g2UvHLnM3I2XRtfMaGDL" Message-ID: <1312550081.12447.3.camel@BMThinkPad.lan.bluematt.me> Mime-Version: 1.0 Resent-From: Matt Corallo Resent-To: bitcoin-development Date: Fri, 05 Aug 2011 23:30:50 +0200 X-Mailer: Evolution 2.32.2 X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.9 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1QpRyt-00072B-El Subject: Re: [Bitcoin-development] Double spend detection to speed up transaction trust X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2011 21:31:00 -0000 --=-g2UvHLnM3I2XRtfMaGDL Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2011-08-05 at 14:03 +0100, Andy Parkins wrote: > I'm arguing that "number of connection slots" isn't the best metric; so t= hat=20 > wouldn't matter. Just keep accepting incoming connections (with some san= ity=20 > limit of course) until you've allocated your bandwidth, not your number o= f=20 > connections. Mike and me were talking about outgoing connection count, not incoming, which is another thing entirely. However, to your point: having 1000 Bitcoin connection is still almost no traffic, the only timt you really hit much traffic is when you get a peer with a client who doesn't have the full chain as they will start downloading the chain maxing your bandwidth. My bandwidth of Bitcoin is something like avg 3GB/month for 125 connections which is nothing. However it has very brief spikes of my entire outgoing bandwidth. Thus, neither bandwidth nor connection count are really good metrics for choosing your number of incoming slots. Matt --=-g2UvHLnM3I2XRtfMaGDL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJOO+zAAAoJEBrh01BD4I5U6mYQAI90jSij/6Wj7DSv1WFmScM6 U5Ycv6H13GrnPZJRdvO4/fgEqRfPmJbv5UvVEyQ85VQ9VnQrAOlyEgZgLrLUyokt Br3IHLKx8YijvptWISOq9zmcU9dHefQejczdCONljMas783zgrFMZJjgSOR0XxRA Z2yt7xrNlcx1Qs7bq7WTBQ/O9N+5OX2b48QSsi5br6QzB2cSoFyighh6pyH3wM6m R65/Wo+XxEHHg0ivEg0t/pUP99rmjsBmZZPJ4qQg2JlC4jwj/yaV9bacwz1+o5pD zAyl/QCweXsQqey3UrRfynWnAwuhVVOh/WumdCCQ/u4Be77L4PyW/wUDQlydcsdP kBtXq82icKVBzBoBtIrk1f+QvAcc95PjrRvfZPhVPJGL4NgK7p1mkaBh67nGzJ4R ZwdxVd9S9hYO1DHtOhe1Y3FP7/tBX3ZUdc1mV0Cxt4x4V3cDnSWIkan4R/EFsRib 6lMy7FiEwXUFbBt9zZmiWKPERSxnOxCZjVdzCD3pGuWQQ1P4eFUn/G8NvltJ7eVr taiHom+Cs5l+UrcQbt7JfO1roi2RJA0xvf9G6GP7eCquAASW7bPG2UT6oOkRdpK5 Sl6AjOWbbphahZ8KWbcS0ov3D70DBZy2sBziHKlq/kufYfbFGM0VVr6TFcQoKrdF PzcWnOEW5NrSQQes2UA2 =08uz -----END PGP SIGNATURE----- --=-g2UvHLnM3I2XRtfMaGDL--