Open
Bug 759040
Opened 12 years ago
Updated 3 years ago
In nsHttpChannel, call mCacheAsyncFunc directly from ReadFromCache instead of dispatching an asynchronous event
Categories
(Core :: Networking: HTTP, defect, P5)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: briansmith, Unassigned)
Details
(Keywords: perf, Whiteboard: [necko-backlog])
AFAICT, we should be able to call mCacheAsyncFunc directly, instead of calling it through AsyncCall(mCacheAsyncFunc), at least in most situations. This should speed things up by avoiding the need to wait for the main thread event queue to be cleared before calling mCacheAsyncFunc.
|
Reporter | |
Updated•12 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Comment 3•3 years ago
|
||
Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: P3 → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•