google-app-engine - Google App Engine - 负载测试中高负载时 throttle_code=4

Question

我正在使用 JMeter 运行一些负载测试，以了解我的应用程序在负载下如何在 Google App Engine (Java) 上执行。

当我遇到大约 100 个虚拟用户时，我的响应时间开始下降，并且我注意到“throttle_code=4”出现在 GAE 日志文件中(见下文)。

谁知道这是什么意思？我从同一个 IP 发出多个请求是否会触发某种自动 DDOS 保护？

谢谢

---- request with"throttle_code=4"; when connecting from JMeter07-05 05:11AM 58.917 /market/1234/history?pricebars=240 200 3651ms 19cpu_ms 35kb Java/1.5.0_16,gzip(gfe)75.101.226.4 - - [05/Jul/2010:05:12:02 -0700] "GET /market/1234/history?pricebars=240 HTTP/1.1" 200 35566 - "Java/1.5.0_16,gzip(gfe)" "ci-pricehistory.appspot.com" ms=3652 cpu_ms=19 api_cpu_ms=0 cpm_usd=0.004527 pending_ms=3570 throttle_code=4I 07-05 05:12AM 02.532uk.co.cityindex.CandleServlet fetch: Loading 240 bars from cache...I 07-05 05:12AM 02.558uk.co.cityindex.CandleServlet fetch: time:47---- request without "throttle" log; when connecting from browser07-05 06:28AM 10.993 /market/1234/history?pricebars=240 200 69ms 19cpu_ms 7kb Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4,gzip(gfe)80.169.172.178 - - [05/Jul/2010:06:28:11 -0700] "GET /market/1234/history?pricebars=240 HTTP/1.1" 200 7572 - "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4,gzip(gfe)" "ci-pricehistory.appspot.com" ms=69 cpu_ms=19 api_cpu_ms=0 cpm_usd=0.001423I 07-05 06:28AM 11.031uk.co.cityindex.CandleServlet fetch: Loading 240 bars from cache...I 07-05 06:28AM 11.055uk.co.cityindex.CandleServlet fetch: time:45

Answer 1

在此处查看(显然)官方 Google 答案，但我不确定它是否完全回答了问题。

It looks like your request is taking 3500ms. We autoscale up the number of instances servicing your requests as long as you maintain average milliseconds/request of 1000ms or under (we recommend 800ms, sub 400ms is optimal). If you run lots of long running requests, we will not spin up new instances for you and you will hit a scaling ceiling.

http://osdir.com/ml/GoogleAppEngine/2010-07/msg00165.html

显然，它们会根据您的“效率”进行节流，但看起来您的原始请求只有 69 毫秒。您的应用程序的平均 ms/req 是否可能由于其他请求而更高？这似乎是一种奇怪的策略 NOT spin up because your app is slow 如果你的应用程序很慢是因为它还没有启动...

我注意到的另一件事是，您通过 JMeter 的测试请求是 35kb，而另一个请求是 7kb - 您的应用程序的数据在测试负载下是否增加？标题堆积如山？