d1cce869ed
Added support for "megabit" and related bandwidth units in annex.stalldetection and everywhere else that git-annex parses data units. Note that the short form is "Mbit" not "Mb" because that differs from "MB" only in case, and git-annex parses units case-insensitively. It would be horrible if two different versions of git-annex parsed the same value differently, so I don't think "Mb" can be supported. See comment for bonus sad story from my childhood. Sponsored-by: Nicholas Golder-Manning
17 lines
924 B
Markdown
17 lines
924 B
Markdown
Download speed is displayed in bytes/second, but in some situations, it
|
|
would be better to use bits/second, eg Mbps and Kbps rather than MiB/s and
|
|
KiB/s.
|
|
|
|
I noticed this now that I have an internet connection that is
|
|
capable of 150-200 Mbps, but varies widely (satellite). While I could think
|
|
of that as 19-25 MiB/s those are less round numbers and harder to remember
|
|
and match up with the other bandwidth displays.
|
|
|
|
This might make sense as a per-remote configurable value. Allowing
|
|
using MiB/s for a hard drive and Mbps for a network remote. --[[Joey]]
|
|
|
|
> I've implemented bandwidthUnits now, but it's not used for display yet.
|
|
> It is possible to specify such units in eg annex.stalldetection now.
|
|
> Note that it uses Mbit, not Mb because that is just confusingly close to
|
|
> "MB" and git-annex parses data units case insensitively. So the actual
|
|
> display will end up being "Mbit/s" rather than Mbps probably. --[[Joey]]
|