|
Post by nateroiger on Aug 19, 2021 15:15:28 GMT
Requesting that Port or PortMetrics add information on the current throughput (GBps), broken down by ingress (Rx) and egress (Tx) values. This can be particularly useful when analyzing bottlenecks for various port types.
The Port v1.4 definition contains CurrentBandwidthGbps and MaxBandwidthGbps, but I believe this is only reporting the negotiated & capable speeds, not any throughput performance metric.
The PortMetric v1.1.0 contains TxBytes and RxBytes. While this can be captured into a metric report and then the throughput is derived, it would be nice to just read the current throughput without capturing multiple metric reports.
I suggest gigaBYTES over gigaBITS as byte-based values seem to be more common and useful in a reporting metric, but elsewhere in the spec ( gigaBITS is used. Whatever the standard committee decides is fine.
|
|
|
Post by jautor on Aug 24, 2021 22:50:40 GMT
We'll take a look at this - but the issue is whether or not the manufacturers will actually support and implement that functionality. It's easy for us to describe in schema, but if no one implements it (and most of the PortMetrics property values come directly from hardware counters), we're doing folks a disservice because they'll attempt to code for something they never find...
And you are correct that the CurrentBandwidthGbps and MaxBandwidthGbps are the negotiated/link speeds and not a performance metric.
Jeff
|
|