-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bandwidth metering on streams #969
Conversation
3689d9a
to
f0031af
Compare
|
||
var StatsCmd = &cmds.Command{ | ||
Helptext: cmds.HelpText{ | ||
Tagline: "Query IPFS daemon statistics", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe just Query IPFS daemon statistics
-- we could have other stats there later, like number of objects stored on the repo, etc.
@whyrusleeping done with CR.
|
Fails race. ideally would drop down goroutine number back down. otherwise, need to lower numbers in
|
feb204d
to
2ac344b
Compare
2ac344b
to
f8b64c9
Compare
7f25f57
to
2c8cb9f
Compare
humanize bandwidth output instrument conn.Conn for bandwidth metrics add poll command for continuous bandwidth reporting move bandwidth tracking onto multiaddr net connections another mild refactor of recording locations address concerns from PR lower mock nodes in race test due to increased goroutines per connection
LGTM RFM |
Add in bandwidth tracking per peer, per protocol, and overall. Also have a basic CLI command to access this data.
Query IPFS daemon statistics
bw --poll
seems more natural.--period=<duration>
flag in bw-pollndjson
in cmds commands lib should use ndjson #982SetConnWrapper
on listener