Open
Bug 1560602
Opened 5 years ago
Updated 2 years ago
[network markers] requests with a cache hit don't have timings reported.
Categories
(Core :: Gecko Profiler, enhancement, P2)
Core
Gecko Profiler
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox69 | --- | affected |
People
(Reporter: julienw, Unassigned)
References
(Blocks 1 open bug)
Details
Looking at some profiles we saw that we don't have the timings reported for requests answered with a cache hit.
|
Reporter | |
Updated•5 years ago
|
Type: defect → enhancement
Priority: -- → P2
|
|
Reporter | |
Comment 1•5 years ago
|
||
Here we want to record timings specific to cache requests.
We can create a new structure for this, NeckoTimingStruct that would keep everything that's not part of the existing TimingStruct.
NeckoTimingStruct would be created only if the profiler is running.
|
||
Comment 2•5 years ago
|
||
The moment we request a cache entry is here, the moment we get it is here and the moment we read the first byte of it (that does not correspond to the moment we have the entry in hands :)) is here and when request == mCachePump.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•