原始文献 / 论坛帖 / Re: Proof-of-work difficulty increasing
Re: Proof-of-work difficulty increasing
Bitcointalk · 2010-02-17 17:58:03 UTC
引用自：Sabunir，2010 年 2 月 16 日 08:51:51 AM（https://bitcointalk.org/index.php?topic=43.msg372#msg372）
可能跟我的连接延迟特别高有关（平均 2000ms 以上）
双向 2 秒延迟，挖矿成功率损失不到 1%。
引用自：Sabunir，2010 年 2 月 16 日 08:51:51 AM（https://bitcointalk.org/index.php?topic=43.msg372#msg372）
和/或丢包率高（有时丢包 10%）？
应该没问题，但我不确定。协议设计成能 resync 到下一条消息，收不到的消息会向所有连着的节点反复索取。漏了块的话，每进来一个新块、发现有缺口，它也会继续要。正式发布前我做过测试，重负载下随机丢 1/4 的消息，能整夜跑下来没有节点卡死。
英文原文
Quote from: Sabunir on February 16, 2010, 08:51:51 AM（https://bitcointalk.org/index.php?topic=43.msg372#msg372）. Perhaps it has to do with my connection's very high latency (2000ms or more on average)
2 seconds of latency in both directions should reduce your generation success by less than 1%.
Quote from: Sabunir on February 16, 2010, 08:51:51 AM（https://bitcointalk.org/index.php?topic=43.msg372#msg372）and/or my high packet loss (sometimes up to 10% loss)?
Probably OK, but I'm not sure. The protocol is designed to resync to the next message, and messages get re-requested from all the other nodes you're connected to until received. If you miss a block, it'll also keep requesting it every time another blocks comes in and it sees there's a gap. Before the original release I did a test dropping 1 out of 4 random messages under heavy load until I could run it overnight without any nodes getting stuck.