Integrate SharedSubResourceCache into DevTools network monitor
Categories
(DevTools :: Netmonitor, task)
Tracking
(firefox132 fixed)
Tracking | Status | |
---|---|---|
firefox132 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
(Blocks 2 open bugs)
Details
Attachments
(12 files, 2 obsolete files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Similar to bug 1722759, we have in-process cache for CSS (mozilla::SharedStyleSheetCache), and JS (mozilla::dom::SharedScriptCache, preffed off by default).
When those cache is used, the request doesn't go to necko, and the network request is not recorded in the DevTools Network Monitor.
We should integrate the SharedSubResourceCache's result into Network Monitor, so that the cached case is also shown there, in the same way as image's cache.
bug 1899734 is similar issue for performance API, which I already have a patch stack to fix.
I'll look into this after the bug.
Assignee | ||
Updated•25 days ago
|
Assignee | ||
Comment 1•24 days ago
|
||
The network monitor code seems to require an nsIHttpChannel, and the image loader is creating a dummy channel with dummy header for the cached case.
If we follow that style, it means the SharedSubResourceCache
's cached case (either complete or pending/loading) also need to create a dummy channel (for the first load in the document).
I wonder if there can be some performance impact, or there can be some other concern.
emilio, can I have your opinion?
Do you see any possible issue?
Comment 2•24 days ago
|
||
:shasha is looking at this in bug 1884876... I think creating a cache is ok as long as we do it only conditional on DevTools being open (which is the HasObservers
call she has there).
Assignee | ||
Comment 3•24 days ago
|
||
Thanks!
Indeed it's the same issue. I'll close this bug and look into the patch there.
Assignee | ||
Comment 4•21 days ago
|
||
Actually, there are some more work necessary to make all cases (loading/pending caches, and non-<link>
cases) handled for sub resource cache.
Assignee | ||
Comment 5•13 days ago
|
||
Updated•13 days ago
|
Assignee | ||
Comment 6•13 days ago
|
||
Assignee | ||
Comment 7•13 days ago
|
||
Assignee | ||
Comment 8•13 days ago
|
||
Assignee | ||
Comment 9•13 days ago
|
||
Assignee | ||
Comment 10•13 days ago
|
||
Assignee | ||
Comment 11•13 days ago
|
||
Assignee | ||
Comment 12•13 days ago
|
||
Assignee | ||
Comment 13•13 days ago
|
||
Assignee | ||
Comment 14•13 days ago
|
||
Assignee | ||
Comment 15•13 days ago
|
||
Assignee | ||
Comment 16•13 days ago
|
||
Assignee | ||
Comment 17•13 days ago
|
||
Assignee | ||
Comment 18•13 days ago
|
||
bug 1899734 will add cached-data handling, and we can add more info there for the HTTP headers for DevTools/WebDriver notifications as well, in bug 1915626.
We'll still need to use different conditions for triggering the notification, because the notification with channel is high-cost, while the performance API integration doesn't require the channel and also it needs to be performed unconditionally.
Also bug 1919218 is for unifying the notifications for image/css/js, with fixing the consumers at the same time.
Updated•12 days ago
|
Updated•12 days ago
|
Assignee | ||
Comment 19•11 days ago
|
||
Updated•10 days ago
|
Comment 20•6 days ago
|
||
Comment 21•6 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/248f51d7b630
https://hg.mozilla.org/mozilla-central/rev/2a7c72f1d4a2
https://hg.mozilla.org/mozilla-central/rev/9665162d9882
https://hg.mozilla.org/mozilla-central/rev/87e5eee230b9
https://hg.mozilla.org/mozilla-central/rev/77456d1f70d0
https://hg.mozilla.org/mozilla-central/rev/98a32fe3d03f
https://hg.mozilla.org/mozilla-central/rev/e327d3a05d80
https://hg.mozilla.org/mozilla-central/rev/a1e031eb440d
https://hg.mozilla.org/mozilla-central/rev/4e0d1427f4af
https://hg.mozilla.org/mozilla-central/rev/71f9b6e37759
https://hg.mozilla.org/mozilla-central/rev/1f30191c85d8
https://hg.mozilla.org/mozilla-central/rev/331d2711a95b
Description
•