3 ms·
“You have a few options for getting a great picture of how your system performs: • Good old analysis.” I’ve been trying to do that (because it seemed the only
by Someone 6y ago
“You have a few options for getting a great picture of how your system performs:
• Good old analysis.”
I’ve been trying to do that (because it seemed the only realistic method for figuring out how to cost optimize a cloud setup (should we have more smaller API servers or a few big ones? One or two databases? (When) should we scale down instances in less busy times? ...), but didn’t get far.
Being mathematically schooled, I went for queueing theory. That isn’t simple, but not the main stumbling block. The complexity of cloud infrastructure is. Figuring out how many simultaneous requests AWS load balancers/Kubernetes can handle, what delays they introduce, how they route calls (round-robin/random/...) how large their queues are, how Kubernetes scales down/up instances is quite a challenge.
So, has anybody collected ballpark numbers for these kinds of things, or hints on what can be ignored in the setup? How do people handle cost optimization of cloud instances?
Or do people just bring up variations on the infrastructure, benchmark them, and, when getting bored/running out of time/having found something that isn’t too expensive, stick to the best configuration found?
- heavenlyblue 6y ago> but didn’t get far. So what did you do?