4 ms·
Couldn't agree more. As I (poorly) tried to point out in my earlier off-the-cuff comment, requests-per-second is a meaningless measure without the context of th
by scoot 13y ago
Couldn't agree more. As I (poorly) tried to point out in my earlier off-the-cuff comment, requests-per-second is a meaningless measure without the context of the size of those requests. The Forbes repost and the original google marketing article are both vague on details, and appear to conflate requests-per-second with throughput.
- p3rfguy 13y agoMarketing 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 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
- simplemath 13y agoI wish there were more posts here on HN where the OP linked items such as yours, but alas, clickbait rules apply. I think I'm going to play with your script package over the long weekend in our dev cluster - Thanks! And nice work!
- snrip 13y agoI saw you dropped this line in the comments under the article. Guess this would be a better place for it :) "PS... Cloud Performance is hiring :)"