node: Further increase the rate-limit defaults

The rate-limitter gets hit on connect, due to historical gossip messages
being exchanged. This results in a high initial burst that needs to be
accounted for.
This commit is contained in:
cloudhead 2024-05-02 13:10:32 +02:00
parent 5ffbf7545f
commit a54180199e
No known key found for this signature in database
3 changed files with 12 additions and 12 deletions

View File

@ -38,12 +38,12 @@ $ rad config
"maxOpenFiles": 4096, "maxOpenFiles": 4096,
"rate": { "rate": {
"inbound": { "inbound": {
"fillRate": 2.0, "fillRate": 5.0,
"capacity": 128 "capacity": 1024
}, },
"outbound": { "outbound": {
"fillRate": 5.0, "fillRate": 10.0,
"capacity": 256 "capacity": 2048
} }
}, },
"connection": { "connection": {

View File

@ -101,12 +101,12 @@ mod routes {
"maxOpenFiles": 4096, "maxOpenFiles": 4096,
"rate": { "rate": {
"inbound": { "inbound": {
"fillRate": 2.0, "fillRate": 5.0,
"capacity": 128 "capacity": 1024
}, },
"outbound": { "outbound": {
"fillRate": 5.0, "fillRate": 10.0,
"capacity": 256 "capacity": 2048
} }
}, },
"connection": { "connection": {

View File

@ -168,12 +168,12 @@ impl Default for RateLimits {
fn default() -> Self { fn default() -> Self {
Self { Self {
inbound: RateLimit { inbound: RateLimit {
fill_rate: 2.0, fill_rate: 5.0,
capacity: 128, capacity: 1024,
}, },
outbound: RateLimit { outbound: RateLimit {
fill_rate: 5.0, fill_rate: 10.0,
capacity: 256, capacity: 2048,
}, },
} }
} }