Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article provides brief information on the interface traffic graph reflecting in kpbs instead of bps traffic.
All NPM versions
The amount of traffic passing through the interface is too high, and the limit unit (1kbps ~ 1000 bps) therefore, the chart will intelligently convert and show you the next unit kbps and calculate the conversion values for you.
kbps or Kilobits Per Second - One kilobit is 1000 bits, and bits are the smallest possible unit of information
If you notice the report graph is starting from bps, however, it is taking the jump to kbps as the amount of traffic passing through is very high and there is no logic to still keep showing in bps in such a high values number.
Now if you notice the below graph is showing traffic in bps for this interface as there is very less traffic passing through and it can be easily been allocated under bps units as there is no need to be use of kbps unit conversion on this stage.
Interface went up to 75 kbps if you convert it will be 75000 bps in the graph which doesn't makes any logic to still keep showing in the same conversion rates where the next conversion unit is available which is easy to understand therefor it will be change to 75 kbps automatically .
So as Network Engineer if i be looking at this graphs i will easily understand how much bps averagely is passing through the interface by simply adding conversation rates as above if required or by understanding the unit conversion rates.
Other simple logic is will you take one note of 100$ or 100 notes of 1$ ? Inelegant preference is 1 note of 100$ .