You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to better monitor adoption of Boost as well as the various retrieval protocols (graphsync, bitswap, http) so we can better support SPs.
Proposal
Collect libp2p agent version
The libp2p agent versions should give us a better understanding of who is using lotus/venus/boost/etc and what version adoption of Boost looks like. We already run identify to get the protocols, so we just need to track the agent versions.
This could just be a simple map counter we print out.
Collect supported retrieval protocols
#723 added support for checking supported retrieval protocols over libp2p. We should run this check to see which protocols each SP supports as we crawl the network.
Example existing output
...
Total Boost nodes: 309
Total Boost raw power: 673768287275843584
Total Boost quality adj power: 2497977391189557248
Total Lotus Markets nodes: 591
Total SPs with minimum power: 3588
Total Indexer nodes: 721
Example updated output
...
Total Boost nodes: 309
Total Boost raw power: 673768287275843584
Total Boost quality adj power: 2497977391189557248
Total Lotus Markets nodes: 591
Total SPs with minimum power: 3588
Total Indexer nodes: 721
Retrieval Protocol Support:
graphsync: 309
http: 25
bitswap: 19
Agent Versions:
boost/1.6.0: 250
boost/1.6.1-rc1: 10
lotus/1.20.3: 489
otherversionhere: x
...
The text was updated successfully, but these errors were encountered:
jacobheun
changed the title
Update boostx stats command to include agent version breakdown
Update boostx stats command to include agent version & retrieval support breakdown
Mar 17, 2023
Summary
We want to better monitor adoption of Boost as well as the various retrieval protocols (graphsync, bitswap, http) so we can better support SPs.
Proposal
Collect libp2p agent version
The libp2p agent versions should give us a better understanding of who is using lotus/venus/boost/etc and what version adoption of Boost looks like. We already run identify to get the protocols, so we just need to track the agent versions.
This could just be a simple map counter we print out.
Collect supported retrieval protocols
#723 added support for checking supported retrieval protocols over libp2p. We should run this check to see which protocols each SP supports as we crawl the network.
Example existing output
Example updated output
The text was updated successfully, but these errors were encountered: