As mentioned in the docs, the calculator could use one of the following:
high-level:
latency profiles: some sort of pre-made latency profiles which chooses "low latency < 100ms", med latency "< 250ms p99" and etc. Then, the calculator chooses the right disk and buffer based on that.
avg-max throughput: allow users to define their avg throughput for cost calculating purposes (e.g network charges) but configure a max that the cluster must be able to support without trouble at all times
low-level:
an IOPS utilization buffer. e.g ensure we only use 50% of provisioned IOPS
Please authenticate to join the conversation.
In Review
π‘ Issues / Feedback
About 1 year ago

2minutestreaming
Get notified by email when there are changes.
In Review
π‘ Issues / Feedback
About 1 year ago

2minutestreaming
Get notified by email when there are changes.