Remove maxuploadtargets recommended minimum

Github-Pull: #8712
Rebased-From: 1b6bcdd3aa
pull/262/head
Jonas Schnelli 8 years ago committed by Wladimir J. van der Laan
parent a5ec248323
commit 23feab1f38

@ -19,8 +19,7 @@ This is *not* a hard limit; only a threshold to minimize the outbound
traffic. When the limit is about to be reached, the uploaded data is cut by no traffic. When the limit is about to be reached, the uploaded data is cut by no
longer serving historic blocks (blocks older than one week). longer serving historic blocks (blocks older than one week).
Keep in mind that new nodes require other nodes that are willing to serve Keep in mind that new nodes require other nodes that are willing to serve
historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB historic blocks.
per day)**
Whitelisted peers will never be disconnected, although their traffic counts for Whitelisted peers will never be disconnected, although their traffic counts for
calculating the target. calculating the target.

@ -2226,11 +2226,7 @@ void CNode::RecordBytesSent(uint64_t bytes)
void CNode::SetMaxOutboundTarget(uint64_t limit) void CNode::SetMaxOutboundTarget(uint64_t limit)
{ {
LOCK(cs_totalBytesSent); LOCK(cs_totalBytesSent);
uint64_t recommendedMinimum = (nMaxOutboundTimeframe / 600) * MAX_BLOCK_SERIALIZED_SIZE;
nMaxOutboundLimit = limit; nMaxOutboundLimit = limit;
if (limit > 0 && limit < recommendedMinimum)
LogPrintf("Max outbound target is very small (%s bytes) and will be overshot. Recommended minimum is %s bytes.\n", nMaxOutboundLimit, recommendedMinimum);
} }
uint64_t CNode::GetMaxOutboundTarget() uint64_t CNode::GetMaxOutboundTarget()

Loading…
Cancel
Save