「Satoshi Client Block Exchange」を編集中
この編集を取り消せます。
下記の差分を確認して、本当に取り消していいか検証してください。よろしければ変更を保存して取り消しを完了してください。
最新版 | 編集中の文章 | ||
30行目: | 30行目: | ||
したがって、両方のノードが互いに話し合っている2つのノードは、特にどちらか一方が遠く、もう一方が他方よりはるかに遠い場合に、最適ではない対話につながる可能性があります。 | したがって、両方のノードが互いに話し合っている2つのノードは、特にどちらか一方が遠く、もう一方が他方よりはるかに遠い場合に、最適ではない対話につながる可能性があります。 | ||
− | == | + | == Flood Limit Effects == |
+ | Even with the batching mechanism described above, there are scenarios | ||
+ | that occur that result in the remote node overflowing the local receive | ||
+ | buffer while blocks are being exchanged. | ||
− | + | For example, if a remote node is "catching up", it will advertise each block | |
+ | it processes to the local node in certain circumstances (see above [17]). | ||
+ | The local node will request each of those blocks right away. There is no | ||
+ | protection against the local node requesting too many of these blocks. | ||
+ | The remote node will send all blocks requested. There is no protection | ||
+ | against the remote node sending too many blocks before the local node has | ||
+ | time to process them, in this circumstance. | ||
− | + | The local receive buffer can fill up. When the local node notices a receive | |
+ | buffer is full, it disconnects that node connection.[18] | ||
+ | If sets the fDisconnect flag, and once the buffers are empty[19], the | ||
+ | socket is closed. | ||
− | |||
==パフォーマンス == | ==パフォーマンス == |