Open
Bug 1666886
Opened 4 years ago
Updated 2 years ago
Ensure we exercise QUIC/http2/http3/TLS code in PGO runs
Categories
(Firefox Build System :: General, enhancement, P4)
Firefox Build System
General
Tracking
(Not tracked)
NEW
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
When I did a brief overview of our PGO infra for our perf folks, they flagged up that it does not appear that we exercise much of our network stack as part of the PGO runs.
In theory, it should be possible to exercise our network/TLS stack and eke out some performance wins in that area. Although the PGO runs use an http server to serve the JS/DOM tests they run, AFAICT there will be no (or almost no, if we do any background requests that we've not redirected to /dev/null / localhost) use of TLS, or httpv2/QUIC/http3 etc.
As we already merge serveral profraw
files, we could use xpcshell/browsertime/mach-perftest or other frameworks to gather this info if that's easier than integrating it into the existing pgo building run script.
Reporter | ||
Updated•4 years ago
|
Type: defect → enhancement
Updated•4 years ago
|
Severity: -- → S4
Priority: -- → P4
You need to log in
before you can comment on or make changes to this bug.
Description
•