You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
In the Create modal, we currently display values using decimal/metric units instead of binary when representing bytes. We should update our units of measure to use binary units following the PF guidelines.
Specifically, these updates are needed:
label
current text
proposed text
Ingress/Egress
up to 2 MB/second each
up to 2 MiB/second each
Note that PF guidelines recommend MiBps for rate, but we have another value represented as "connections/second" and therefore use "/second" here for consistency
Storage
up to 60 GB
up to 60 GiB
Message size
up to 1 MB
up to 1 MiB
In a discussion related to metrics and the units of measure that we use, the following feedback was provided:
the Ingress/Egress is actually set to 2MiB/second
for Storage, we could change advertise as 60GiB, since it's actually somewhere between 80-90GiB in reality
the max.message.bytes is at the default of 1048588, which is 1MiB, so that one could also be changed
Note that Topic properties currently use binary units as well.
Screencap of current Create modal
The text was updated successfully, but these errors were encountered:
In the Create modal, we currently display values using decimal/metric units instead of binary when representing bytes. We should update our units of measure to use binary units following the PF guidelines.
Specifically, these updates are needed:
In a discussion related to metrics and the units of measure that we use, the following feedback was provided:
Note that Topic properties currently use binary units as well.
Screencap of current Create modal
The text was updated successfully, but these errors were encountered: