Open
Bug 1348242
Opened 8 years ago
Updated 2 years ago
Use multiple read threads for HTTP cache I/O
Categories
(Core :: Networking: Cache, enhancement, P3)
Core
Networking: Cache
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [necko-backlog])
No idea if this is just a simple thing to do or it can break stuff a lot.
Quick testing (CrystalDiskMark, win10) shows that reading (random 4k) with 10 threads is 2x faster on HDD and 7x faster on SSD. Writing seems to be unaffected (system cache works in our benefit already).
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 3•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
Reporter | |
Comment 4•6 years ago
|
||
We are seeing our current single cache thread flood when there is a large number of css and sync scripts on a page. One example: https://www.facebook.com/DwayneJohnson/ with ~140 js files and ~27 css files, all blockers with the same priority treatment by the cache open and read queue.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•