2023-04-03 05:35:11 +00:00
|
|
|
[package]
|
|
|
|
|
name = "watch"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
edition = "2018"
|
|
|
|
|
|
|
|
|
|
[lib]
|
|
|
|
|
name = "watch"
|
|
|
|
|
path = "src/lib.rs"
|
|
|
|
|
|
|
|
|
|
[[bin]]
|
|
|
|
|
name = "watch"
|
|
|
|
|
path = "src/main.rs"
|
|
|
|
|
|
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
|
|
|
|
clap = "2.33.3"
|
|
|
|
|
log = "0.4.14"
|
|
|
|
|
env_logger = "0.9.0"
|
|
|
|
|
types = { path = "../consensus/types" }
|
|
|
|
|
eth2 = { path = "../common/eth2" }
|
|
|
|
|
beacon_node = { path = "../beacon_node"}
|
|
|
|
|
tokio = { version = "1.14.0", features = ["time"] }
|
2023-07-17 00:14:15 +00:00
|
|
|
axum = "0.6.18"
|
2023-04-03 05:35:11 +00:00
|
|
|
hyper = "0.14.20"
|
|
|
|
|
serde = "1.0.116"
|
|
|
|
|
serde_json = "1.0.58"
|
|
|
|
|
reqwest = { version = "0.11.0", features = ["json","stream"] }
|
|
|
|
|
url = "2.2.2"
|
|
|
|
|
rand = "0.7.3"
|
|
|
|
|
diesel = { version = "2.0.2", features = ["postgres", "r2d2"] }
|
|
|
|
|
diesel_migrations = { version = "2.0.0", features = ["postgres"] }
|
|
|
|
|
byteorder = "1.4.3"
|
|
|
|
|
bls = { path = "../crypto/bls" }
|
|
|
|
|
hex = "0.4.2"
|
|
|
|
|
r2d2 = "0.8.9"
|
|
|
|
|
serde_yaml = "0.8.24"
|
|
|
|
|
|
|
|
|
|
[dev-dependencies]
|
|
|
|
|
tokio-postgres = "0.7.5"
|
|
|
|
|
http_api = { path = "../beacon_node/http_api" }
|
|
|
|
|
beacon_chain = { path = "../beacon_node/beacon_chain" }
|
|
|
|
|
network = { path = "../beacon_node/network" }
|
2023-08-28 00:55:28 +00:00
|
|
|
# TODO: update to 0.15 when released: https://github.com/testcontainers/testcontainers-rs/issues/497
|
|
|
|
|
testcontainers = { git = "https://github.com/testcontainers/testcontainers-rs/", rev = "0f2c9851" }
|
2023-04-03 05:35:11 +00:00
|
|
|
unused_port = { path = "../common/unused_port" }
|
Use `BeaconProcessor` for API requests (#4462)
## Issue Addressed
NA
## Proposed Changes
Rather than spawning new tasks on the tokio executor to process each HTTP API request, send the tasks to the `BeaconProcessor`. This achieves:
1. Places a bound on how many concurrent requests are being served (i.e., how many we are actually trying to compute at one time).
1. Places a bound on how many requests can be awaiting a response at one time (i.e., starts dropping requests when we have too many queued).
1. Allows the BN prioritise HTTP requests with respect to messages coming from the P2P network (i.e., proiritise importing gossip blocks rather than serving API requests).
Presently there are two levels of priorities:
- `Priority::P0`
- The beacon processor will prioritise these above everything other than importing new blocks.
- Roughly all validator-sensitive endpoints.
- `Priority::P1`
- The beacon processor will prioritise practically all other P2P messages over these, except for historical backfill things.
- Everything that's not `Priority::P0`
The `--http-enable-beacon-processor false` flag can be supplied to revert back to the old behaviour of spawning new `tokio` tasks for each request:
```
--http-enable-beacon-processor <BOOLEAN>
The beacon processor is a scheduler which provides quality-of-service and DoS protection. When set to
"true", HTTP API requests will queued and scheduled alongside other tasks. When set to "false", HTTP API
responses will be executed immediately. [default: true]
```
## New CLI Flags
I added some other new CLI flags:
```
--beacon-processor-aggregate-batch-size <INTEGER>
Specifies the number of gossip aggregate attestations in a signature verification batch. Higher values may
reduce CPU usage in a healthy network while lower values may increase CPU usage in an unhealthy or hostile
network. [default: 64]
--beacon-processor-attestation-batch-size <INTEGER>
Specifies the number of gossip attestations in a signature verification batch. Higher values may reduce CPU
usage in a healthy network whilst lower values may increase CPU usage in an unhealthy or hostile network.
[default: 64]
--beacon-processor-max-workers <INTEGER>
Specifies the maximum concurrent tasks for the task scheduler. Increasing this value may increase resource
consumption. Reducing the value may result in decreased resource usage and diminished performance. The
default value is the number of logical CPU cores on the host.
--beacon-processor-reprocess-queue-len <INTEGER>
Specifies the length of the queue for messages requiring delayed processing. Higher values may prevent
messages from being dropped while lower values may help protect the node from becoming overwhelmed.
[default: 12288]
```
I needed to add the max-workers flag since the "simulator" flavor tests started failing with HTTP timeouts on the test assertions. I believe they were failing because the Github runners only have 2 cores and there just weren't enough workers available to process our requests in time. I added the other flags since they seem fun to fiddle with.
## Additional Info
I bumped the timeouts on the "simulator" flavor test from 4s to 8s. The prioritisation of consensus messages seems to be causing slower responses, I guess this is what we signed up for 🤷
The `validator/register` validator has some special handling because the relays have a bad habit of timing out on these calls. It seems like a waste of a `BeaconProcessor` worker to just wait for the builder API HTTP response, so we spawn a new `tokio` task to wait for a builder response.
I've added an optimisation for the `GET beacon/states/{state_id}/validators/{validator_id}` endpoint in [efbabe3](https://github.com/sigp/lighthouse/pull/4462/commits/efbabe32521ed6eb3564764da4e507d26a1c4bd0). That's the endpoint the VC uses to resolve pubkeys to validator indices, and it's the endpoint that was causing us grief. Perhaps I should move that into a new PR, not sure.
2023-08-08 23:30:15 +00:00
|
|
|
task_executor = { path = "../common/task_executor" }
|
