mab122
/
radicle-heartwood-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

node: Increase default rate-limiter config 

With the increase in traffic on the network after launch, the old
defaults don't make sense anymore.

Longer term, we should look into throttling outgoing messages as well,
prioritizing original messages over relayed messages.
This commit is contained in:
cloudhead 2024-04-30 14:46:30 +02:00
parent afe13b9e47
commit abf89438ea
No known key found for this signature in database
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
radicle-cli/examples/rad-config.md
View File

@ -38,12 +38,12 @@ $ rad config
"maxOpenFiles": 4096,
"rate": {
"inbound": {
"fillRate": 0.2,
"capacity": 32
"fillRate": 2.0,
"capacity": 128
},
"outbound": {
"fillRate": 1.0,
"capacity": 64
"fillRate": 5.0,
"capacity": 256
}
},
"connection": {

8
radicle-httpd/src/api/v1/profile.rs
View File

@ -101,12 +101,12 @@ mod routes {
"maxOpenFiles": 4096,
"rate": {
"inbound": {
"fillRate": 0.2,
"capacity": 32
"fillRate": 2.0,
"capacity": 128
},
"outbound": {
"fillRate": 1.0,
"capacity": 64
"fillRate": 5.0,
"capacity": 256
}
},
"connection": {

8
radicle/src/node/config.rs
View File

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