-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESI/Statification of CSS/JS increases response time, even when cached #935
Comments
I quickly looked at the response, and it seems to be cached. but if you look a the way curl serves the response, you can see it stalls before:
which is the new static-cache-key-resolver. I checked runtime, it's not invoking the backend, so this seems to be cached as well, but still adds a bit of overhead to the request processing. while the ESI's are cool, I don't think they help the overall performance. my gut feeling is, that every esi adds about 100ms to the response time. so imaging a page with many static includes, it would be very slow.... try:
|
I don't think this is what's happening. The average response time definitely has gone up, but requesting either of the URLs mentioned in this thread repeatedly is fast. As Pingdom is rotating between locations (and thus Fastly edge nodes), we might be seeing that the ESI is being processed in the wrong location: edge, cluster, shield? (I don't know) |
A little bit of analysis shows:
Quick and obvious conclusion: something in hlx code has changed and slows down the same project code. Considering the number of features we introduced, only performance tracing could revealing where it is slower than before. I |
won't fix for helix 2. irrelevant for helix 3. |
Looking at the status page it looks like the response times more than doubled recently for the project helix homepage
The text was updated successfully, but these errors were encountered: