A βnormalβ 200 ms seems to be on the high side of things for static files. I am serving a static version of the same "bootstrap-responsive.css" from my application, and I see two types of responses:
- 50-100 ms (most of the time)
- 150-500 ms (sometimes)
Since I have a roundtrip ping of more or less 50 ms for the Google App Engine, it seems the file usually arrives within 50 ms or so.
I would suggest that the response time of 150-300 ms is associated with the external interface of the Google application server, the "cold cache". I suggested that retrieving a file from some persistent storage is associated with higher latencies than if it is in the frontend cache server.
I also suggest that you can hit different frontend servers and get sporadic higher latencies.
Finally, the total perceived latency in the browser should be closely approximated: (tc) ping round trip + tcp / http queue / buffering on the frontend server + file submission time (as shown in your Google application logs) + time to transfer the file.
If the external server is not overloaded and the file is small, the wait time should be close to ping + maintenance time.
In my case, 50 ms (ping) + 35 ms (maintenance) = 85 ms, pretty close to what I see in my browser 95 ms.
Finally, if your application is serving a lot of requests, they may be queued, representing a delay that is not βvisibleβ in the application logs.
source share