Mike Hearn [ARCHIVE] on Nostr: 📅 Original date posted:2011-06-14 🗒️ Summary of this message: Block sizes are ...
📅 Original date posted:2011-06-14
🗒️ Summary of this message: Block sizes are getting large again, causing scalability issues with the 10mb flood control limit. Solutions include raising the limit or lowering the batch size.
📝 Original message: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?
Published at
2023-06-07 01:55:19Event JSON
{
"id": "9b6030ad67cbffae421bba4cb5e546a6b4496a3cdcbf656a4bf2b3f1044cd80b",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686102919,
"kind": 1,
"tags": [
[
"e",
"c7ded9dbb90041897f3725c4854ecb8df42fdac7f8e369231579c6755331b938",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2011-06-14\n🗒️ Summary of this message: Block sizes are getting large again, causing scalability issues with the 10mb flood control limit. Solutions include raising the limit or lowering the batch size.\n📝 Original message:Block sizes have started to get quite large once again. Whilst testing\nchain download today I was disconnected due to going over the 10mb\nflood control limit. Infuriatingly, I can't reproduce this reliably.\nBut at 500 blocks an average of 20kb per block will cause this. As we\ncan see from the block explorer, the average is probably quite close\nto that.\n\nThe flood control seems like a pretty serious scalability limitation.\nI can see a few solutions. One is to raise the limit again. Another is\nto raise the limit and simultaneously lower the batch size. 500 blocks\nin one message means very large messages no matter how big the flood\ncontrol limit is. Going down to 100 or even 50 would hurt chain\ndownload speed quite a bit in high latency environments, but chain\ndownload is already a serious bottleneck.\n\nThoughts?",
"sig": "9b84392593669a2dcb05ad71ef42daaf8edfbc4607293e4e4371503e97ce9d02a3c8cea1aa3d9afca3ae951057b741a337ab3ac3c831ebd87551493fd40e6bd3"
}