Upload Throughput monitor - #1044
Conversation
bring up to date
Co-authored-by: Copilot <copilot@github.com>
| } | ||
|
|
||
| t1=$(get_tx_bytes) | ||
| sleep 1 |
There was a problem hiding this comment.
it seems better to get one value and return it immediately (and do calculation of delta/speed on the web interface side) so as to not block the CGI call for a whole second, especially since the web interface fires off such a call once a second
There was a problem hiding this comment.
One thing I was worried about was handling timing in the browser because variances in the request/response will cause drift in the measurement
There was a problem hiding this comment.
okay it seems good enough now. I added timestamps on each request response
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
marcone
left a comment
marcone
left a comment
There was a problem hiding this comment.
What does this show when it's not archiving? I haven't tried it yet, but if I'm reading the code correctly it will display any value >= 0, so just looking at the tab would be showing something like "Current Upload: 0.2 KB/s (0.0 Mbit/s)" just from refreshing the web interface, which doesn't seem super useful and may be confusing.
|
Yep |
2 participants
Added upload speed monitor on web dashboard. Useful for ensuring archiving is happening at an adequate speed or to diagnose connectivity to archive.