Open
Bug 1944325
Opened 9 months ago
Updated 3 months ago
Testcase generating N websockets spends a lot of time on the Parent-process and is 9x slower than Chrome (N=100K)
Categories
(Core :: Networking: WebSockets, enhancement, P3)
Core
Networking: WebSockets
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file, 1 obsolete file)
|
2.13 KB,
text/html
|
Details |
Open attached testcase.
Enter some large N
Create generate.
N=10000
Nightly: https://share.firefox.dev/3E7wBk7
Chrome: https://share.firefox.dev/4azUjBK
N=100000
Nightly: https://share.firefox.dev/4jBFJ0y
Chrome: Slower
Maybe something to improve?
Disclaimer: I generated this testcase using chatgpt. I have no idea how realistic this is. Feel free to WONTFIX/INVALID.
Blocks: necko-perf
Severity: -- → N/A
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-new]
Updated•9 months ago
|
Priority: P2 → P3
Whiteboard: [necko-triaged][necko-priority-new] → [necko-triaged]
| Reporter | ||
Comment 1•6 months ago
|
||
| Reporter | ||
Updated•6 months ago
|
Attachment #9462258 -
Attachment is obsolete: true
| Reporter | ||
Comment 2•6 months ago
|
||
N=100000
Firefox: https://share.firefox.dev/42AmWwv (19s)
Chrome: https://share.firefox.dev/44NwkhA (2.2s)
| Reporter | ||
Updated•6 months ago
|
Summary: Testcase generating N websockets spends a lot of time on the Parent-process → Testcase generating N websockets spends a lot of time on the Parent-process and is 9x slower than Chrome (N=100K)
You need to log in
before you can comment on or make changes to this bug.
Description
•