Control transaction dispatch rate:

Do not dispatch a transaction received from a peer for
processing, if it has already been dispatched within the
past ten seconds.

Increase the number of transaction handlers that can be in
flight in the job queue and decrease the relative cost for
peers to share transaction and ledger data.

Additionally, make better use of resources by adjusting the
number of threads we initialize, by reverting commit
68b8ffdb63.
This commit is contained in:
Mark Travis
2017-12-09 17:10:54 -08:00
committed by Nikolaos D. Bougalis
parent 6dc79c23ed
commit fbfb4bd74e
8 changed files with 56 additions and 42 deletions

View File

@@ -27,10 +27,10 @@ namespace Resource {
enum
{
// Balance at which a warning is issued
warningThreshold = 500
warningThreshold = 5000
// Balance at which the consumer is disconnected
,dropThreshold = 1500
,dropThreshold = 15000
// The number of seconds until an inactive table item is removed
,secondsUntilExpiration = 300
@@ -40,7 +40,7 @@ enum
,decayWindowSeconds = 32
// The minimum balance required in order to include a load source in gossip
,minimumGossipBalance = 100
,minimumGossipBalance = 1000
// Number of seconds until imported gossip expires
,gossipExpirationSeconds = 30