chainbound / fiber-benchmarks Goto Github PK

Peer analytics by:

• Aggregating outlier transactions by source_peer p2p and investigating correlations
• Evaluate number of unique peers we see by aggregating source p2p via FiberDB

Description

Run fiber-benchmark vs Bloxroute gateway

To Do's

• Deploy full node (TBD which client) on bare metal server
• Run fiber-benchmark

• Bloxroute now allows for gRPC connection also on intro plans, therefore to make benchmarks as accurate as possible we should integrate it.
• Docs here: https://docs.bloxroute.com/streams/newtxs-and-pendingtxs#examples-grpc

It would be useful to benchmark different environments, tiers or regions of Fiber at the same time.
This means adding the ability to have more than 1 fiber source.

Implementation

Since we can already have multiple Fiber endpoints to support the multiplexed client,
we can start by adding a --fiber-only flag that:

1. uses each unique fiberEndpoint to setup a new fiber source (with the same api key for now should be fine)
2. configure a second fiber endpoint as "other source" in TransactionBenchmarker