To be able to do T133646 (test front end performance on commits) we need to have a proxy to cache responses to have as little disturbance in the metrics as possible. Both Facebook and the Chrome team uses that approach when measuring front end performance.
How it will work
- Access a URL through the proxy.
- DNS and assets are loaded from Internet.
- The proxy caches all the assets and the DNS lookup.
- The next access will be served locally from the proxy.
To decrease latency the proxy will run on the same server as the browser that do the testing. The proxy will need to handle HTTP/2 because we want to test it as realistic as possible.
In this task we need to check what kind of proxies we can use (is there something out there already) and test them out, so we have a clear picture on how we can move on.