p3rfguy
Joined 13 years ago
Karma
14
Submissions
5
Member since
Nov 27
Recent submissions
Comment · 13 years ago
Comment · 13 years ago
Throughput is a measure of work over time. So here I was referring to throughput in terms requests per second and not Gb/s. So it was a direct comparison of 1M RPS (Compute Engine Load Balancing) vs 50K RPS (DNS Load Balancing).
Anthony F. Voellm Google Cloud Performance Engineering Manager @p3rfguy
Comment · 13 years ago
Marketing Post.. Ouch :) One of the things I love about working at Google is we in engineering are empowered to share our knowledge. For those wanting the details check out the step-by-step instructions in the Gist (https://gist.github.com/voellm/1370e09f7f394e3be724).
The goal was to measure the speed of scaling and load balancing vs egress. Bigger egress would not change the load balancing decisions.
Anthony F. Voellm Google Cloud Performance Engineering Manager @p3rfguy
Comment · 13 years ago
Thats about right. In hindsight a tcpdump or other trace might have been useful to include.
Anthony F. Voellm Google Cloud Performance Engineering Manager @p3rfguy
Comment · 13 years ago
We really wanted to focus on the scale of operations for this article so we used a full http request / response. The payload of the response was 1 byte.
Anthony F. Voellm Google Cloud Performance Engineering Manager @p3rfguy
Anthony F. Voellm Google Cloud Performance Engineering Manager @p3rfguy