Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
You could try adding this post into #devops and #cloud too btw. It might help the response rate. In personal experience there's no simple way to "know", you can run load testing to get an idea, but ultimately you have to put things into production to see how they respond. If you have a new service you can put traffic from the old service into the new one (without the user noticing) to get some data on the performance expectations. Apart from that, if you know you're expecting heavy load you usually just setup alerts on the service (and scaling rules if necessary) to scale when needed. Hope that helps!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You could try adding this post into #devops and #cloud too btw. It might help the response rate. In personal experience there's no simple way to "know", you can run load testing to get an idea, but ultimately you have to put things into production to see how they respond. If you have a new service you can put traffic from the old service into the new one (without the user noticing) to get some data on the performance expectations. Apart from that, if you know you're expecting heavy load you usually just setup alerts on the service (and scaling rules if necessary) to scale when needed. Hope that helps!