Skip to content
This repository was archived by the owner on Apr 28, 2020. It is now read-only.

Align byte units to tectonic ones. #338

Merged
merged 1 commit into from
Apr 11, 2019
Merged

Conversation

rawagner
Copy link
Contributor

@AyushAmbastha changing storage units to tectonic ones as suggested by @andybraren in #318 (comment) and network to MBps format

@coveralls
Copy link

Pull Request Test Coverage Report for Build 1127

  • 9 of 9 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.007%) to 87.313%

Totals Coverage Status
Change from base Build 1342: -0.007%
Covered Lines: 3216
Relevant Lines: 3530

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 1354

  • 9 of 9 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.007%) to 87.313%

Totals Coverage Status
Change from base Build 1342: -0.007%
Covered Lines: 3216
Relevant Lines: 3530

💛 - Coveralls

@AyushAmbastha
Copy link
Contributor

Hey @rawagner! Thanks and acknowledged :)

});
it('formats cores', () => {
expect(formatCores(2)).toEqual({ value: 2, unit: 'cores' });
});
it('formats net traffic', () => {
expect(formatNetTraffic(3 * 1024 * 1024)).toEqual({ value: 3, unit: 'MiBps' });
expect(formatNetTraffic(3 * 1000 * 1000)).toEqual({ value: 3, unit: 'MBps' });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we show the network in MBps instead of MiBps?

Copy link

@andybraren andybraren Apr 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@suomiy The last time I fell into this rabbit hole (a few months ago) I learned that networking metrics are still generally measured in Mbps (Megabits per second, note the lowercase b) largely because it has long-been the convention that "everyone" uses, even in cloud-oriented consoles where they use *iB units for everything else.

It's not the greatest reason, but it is what users currently expect for networking as far as I know. I personally can't remember ever seeing Mibps used elsewhere, but I'd be happy to be wrong.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The last time I fell into this rabbit hole (a few months ago) I learned that networking metrics are still generally measured in Mbps (Megabits per second, note the lowercase b) largely because it has long-been the convention that "everyone" uses, even in cloud-oriented consoles where they use *iB units for everything else.

Ok then. If it was decided like that.

I personally can't remember ever seeing Mibps used elsewhere, but I'd be happy to be wrong.

A lot of software uses IEC binary units (KiB/s, MiB/s), e.g. curl, torrent clients.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know! As a relative outsider I like KiB/s and MiB/s and would be happy to switch to that if users find it natural. Looking at what OKD and the Prometheus Dashboard currently do, it seems like they're using Kbps, right? They're a little ambiguous.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to me it seems that Prometheus dashboard uses kB/s (kBps)

@atiratree atiratree merged commit 796c0cf into kubevirt:master Apr 11, 2019
@mareklibra mareklibra mentioned this pull request Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants