Open Bug 1348242 Opened 7 years ago Updated 2 months ago

Use multiple read threads for HTTP cache I/O

Categories

(Core :: Networking: Cache, enhancement, P2)

Product:
Core
Component:
Networking: Cache
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: mayhemer, Unassigned)

References

(Blocks 2 open bugs)

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).
(not a CDP bug)
No longer blocks: CDP
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
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.
Keywords: perf
Severity: normal → S3
Blocks: necko-cache, necko-perf
Priority: P3 → P2
You need to log in before you can comment on or make changes to this bug.