From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
Date: Wed, 03 Aug 2011 17:32:00 +0200 [thread overview]
Message-ID: <1312385520.6416.1.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <CAAS2fgQc9a_-Qnv666c4gdkC0+jjk1QwAY8gMQv9Ts74LLaYbg@mail.gmail.com>
On Wed, 2011-08-03 at 10:48 -0400, Gregory Maxwell wrote:
> On Wed, Aug 3, 2011 at 10:39 AM, Mike Hearn <mike@plan99•net> wrote:
> >> There's a bigger problem here honestly. The p2p network is just starved
> >> for connectable slots.
> >
> > Suggestions:
> > - massively increasing all the anti-DoS limits in 0.4, so far they've caused
> > a lot more damage than they solved.
They were redone in .24 to the point that they should not cause any such
issues in the future.
>
> You can't "massively increase" the number of available connection
> slots without risking running nodes on lower memory systems (e.g. VMs)
> out of memory.
>
> Moreover, 125 slots should be more than enough. We need to figure out
> why it isn't.
Agreed.
next prev parent reply other threads:[~2011-08-03 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:04 Mike Hearn
2011-08-03 11:38 ` Matt Corallo
2011-08-03 12:00 ` Mike Hearn
2011-08-03 12:15 ` Johannes Henninger
2011-08-03 12:17 ` Mike Hearn
2011-08-03 12:27 ` Caleb James DeLisle
2011-08-03 12:40 ` Mike Hearn
2011-08-03 14:00 ` Rick Wesson
2011-08-03 14:10 ` Mike Hearn
2011-08-03 14:18 ` Rick Wesson
2011-08-03 14:28 ` Douglas Huff
2011-08-03 14:39 ` Mike Hearn
2011-08-03 14:48 ` Gregory Maxwell
2011-08-03 15:32 ` Matt Corallo [this message]
2011-08-03 14:37 ` Christian Decker
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=1312385520.6416.1.camel@BMThinkPad.lan.bluematt.me \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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