📅 Original date posted:2011-06-14
🗒️ Summary of this message: Bitcoin's flood control limit based on block size is causing scalability issues, with solutions including raising the limit or lowering the batch size.
📝 Original message:Does it make more sense to have the flood limit based on size in bytes
versus # of blocks?
(I'm a n00b, so pardon my ignorance). :)
D.
On Tue, Jun 14, 2011 at 10:44 AM, Mike Hearn <mike at plan99.net> wrote:
> Block sizes have started to get quite large once again. Whilst testing
> chain download today I was disconnected due to going over the 10mb
> flood control limit. Infuriatingly, I can't reproduce this reliably.
> But at 500 blocks an average of 20kb per block will cause this. As we
> can see from the block explorer, the average is probably quite close
> to that.
>
> The flood control seems like a pretty serious scalability limitation.
> I can see a few solutions. One is to raise the limit again. Another is
> to raise the limit and simultaneously lower the batch size. 500 blocks
> in one message means very large messages no matter how big the flood
> control limit is. Going down to 100 or even 50 would hurt chain
> download speed quite a bit in high latency environments, but chain
> download is already a serious bottleneck.
>
> Thoughts?
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Dave Smith [ARCHIVE] /
npub15d…rcn4y
2023-06-07 03:55:22
in reply to nevent1q…hk2y
Author Public Key
npub15dqslu6gl5ttnlxm3wr4v3kazhuc0k4l4m382qzrxs8jjretn8fsrrcn4ySeen on
wss://relay.noswhere.comPublished at
2023-06-07 03:55:22Event JSON
{
"id": "f3032e1ce7cdb6e0b932eb8c9701cace41f7e14487c462865271917ea60757fc",
"pubkey": "a3410ff348fd16b9fcdb8b875646dd15f987dabfaee2750043340f290f2b99d3",
"created_at": 1686102922,
"kind": 1,
"tags": [
[
"e",
"c7ded9dbb90041897f3725c4854ecb8df42fdac7f8e369231579c6755331b938",
"",
"root"
],
[
"e",
"9b6030ad67cbffae421bba4cb5e546a6b4496a3cdcbf656a4bf2b3f1044cd80b",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2011-06-14\n🗒️ Summary of this message: Bitcoin's flood control limit based on block size is causing scalability issues, with solutions including raising the limit or lowering the batch size.\n📝 Original message:Does it make more sense to have the flood limit based on size in bytes\nversus # of blocks?\n\n(I'm a n00b, so pardon my ignorance). :)\n\nD.\n\nOn Tue, Jun 14, 2011 at 10:44 AM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e Block sizes have started to get quite large once again. Whilst testing\n\u003e chain download today I was disconnected due to going over the 10mb\n\u003e flood control limit. Infuriatingly, I can't reproduce this reliably.\n\u003e But at 500 blocks an average of 20kb per block will cause this. As we\n\u003e can see from the block explorer, the average is probably quite close\n\u003e to that.\n\u003e\n\u003e The flood control seems like a pretty serious scalability limitation.\n\u003e I can see a few solutions. One is to raise the limit again. Another is\n\u003e to raise the limit and simultaneously lower the batch size. 500 blocks\n\u003e in one message means very large messages no matter how big the flood\n\u003e control limit is. Going down to 100 or even 50 would hurt chain\n\u003e download speed quite a bit in high latency environments, but chain\n\u003e download is already a serious bottleneck.\n\u003e\n\u003e Thoughts?\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e EditLive Enterprise is the world's most technically advanced content\n\u003e authoring tool. Experience the power of Track Changes, Inline Image\n\u003e Editing and ensure content is compliant with Accessibility Checking.\n\u003e http://p.sf.net/sfu/ephox-dev2dev\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e",
"sig": "23b93183916190d0cb61e02a9468cf1e1c56b9682eee9b431962e0e327fa1588417fcd2e8efd0eb8ec548c2fd2877ace5c7748e4c8afaec4e27dbf2e81c496c8"
}