Testcase calling js modules N times spends a lot of time on the Socket thread and the Cache2 I/O thread (frecency stuff)
Categories
(Core :: Networking, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged] [necko-priority-next])
Attachments
(1 file)
|
1.09 KB,
application/x-zip-compressed
|
Details |
Download the testcase to your locacl machine, and server it via a local HTTP server
Open testcase.html
Click Run.
Bonus: Once the run is complete, click on "Cleanup"
1000: https://share.firefox.dev/4cdVF8n , https://share.firefox.dev/4az5Lhm, https://share.firefox.dev/4rhJ88f
10000: https://share.firefox.dev/4tyPX72, https://share.firefox.dev/4atcxFl
Lots of different things that i see -
- Lots of time spent on the socket thread
- Lots of time spent in cache2 IO thread doing frecency and more things
- Sometimes, the Cleanup will continue to run in the background
This particular testcase has sequential URLs for the modules. In another version of the testcase, the URLs were always fully random. Not sure if changes the profiles materially.
Testcase is 100% artificial, created using chatgpt based on my idea.
(I wanted a testcas that would stress the navigation cache or the storage-and-retrieval of js from the cache. But this is what i end up with.)
|
||
Updated•5 months ago
|
|
Reporter | |
Comment 1•5 months ago
|
||
socket thred usage can be seen in these profiles: https://share.firefox.dev/46hn9WH ,https://share.firefox.dev/4skoCUX
Description
•