Closed
Bug 1923894
Opened 12 days ago
Closed 7 days ago
Add navstart to request start timing to the pageload event
Categories
(Core :: Performance Engineering, enhancement, P3)
Core
Performance Engineering
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox133 | --- | fixed |
People
(Reporter: acreskey, Assigned: sekim)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(1 file)
It would be useful to collect "navigation start" to "request start" in the pageload event as we've observed that this timing is very sensitive to changes in the runtime.
|
Reporter | |
Updated•12 days ago
|
OS: macOS → All
Hardware: x86_64 → All
|
|
Reporter | |
Comment 1•12 days ago
|
||
Necko team is looking at rolling out DoH on Android in late 2024 and since we already store the TRR domain, this could be a good view on the impact on "time to first byte sent."
|
|
Reporter | |
Comment 2•12 days ago
|
||
If folks have any reservations, let me know, otherwise planning on adding this next week or so.
|
||
Updated•7 days ago
|
Assignee: nobody → sekim
Status: NEW → ASSIGNED
|
|
||
Updated•7 days ago
|
Attachment #9431049 -
Attachment description: Bug 1923894 - Collect timing_distribution from navigation start to request start in the pageload event r=acreskey → Bug 1923894 - Collect timing_distribution from navigation start to request start in the pageload event r=acreskey,denispal
Pushed by sekim@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e1401960795b
Collect timing_distribution from navigation start to request start in the pageload event r=acreskey,denispal
|
||
Comment 5•7 days ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 days ago
status-firefox133:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•