Closed
Bug 1147973
Opened 10 years ago
Closed 10 years ago
Detailed disk cache hit rate telemetry is wrong
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
FIXED
mozilla40
| Tracking | Status | |
|---|---|---|
| firefox40 | --- | fixed |
People
(Reporter: michal, Assigned: michal)
References
Details
Attachments
(1 file, 1 obsolete file)
|
2.31 KB,
patch
|
mayhemer
:
review+
|
Details | Diff | Splinter Review |
Entries that are created as new are not reported.
Attachment #8583918 -
Flags: review?(honzab.moz)
Comment 1•10 years ago
|
||
Comment on attachment 8583918 [details] [diff] [review]
fix
Review of attachment 8583918 [details] [diff] [review]:
-----------------------------------------------------------------
::: netwerk/cache2/CacheEntry.cpp
@@ +386,5 @@
> mozilla::MutexAutoUnlock unlock(mLock);
>
> + if (reportMiss) {
> + CacheFileUtils::DetailedCacheHitTelemetry::AddRecord(
> + CacheFileUtils::DetailedCacheHitTelemetry::MISS, TimeStamp());
You are actually filling the gap when we open the file directly (not getting OnFileReady call), right?
Why exactly you don't want to report NETWORK_CACHE_V2_MISS_TIME_MS here? I think to report 0ms is pretty much OK, we want to see how fast we detect a cache miss, no?
| Assignee | ||
Comment 2•10 years ago
|
||
(In reply to Honza Bambas (:mayhemer) from comment #1)
> You are actually filling the gap when we open the file directly (not getting
> OnFileReady call), right?
Right.
> Why exactly you don't want to report NETWORK_CACHE_V2_MISS_TIME_MS here? I
> think to report 0ms is pretty much OK, we want to see how fast we detect a
> cache miss, no?
I wanted to fix hit rate stats without affecting NETWORK_CACHE_V2_MISS_TIME_MS but I'm not against.
Attachment #8583918 -
Attachment is obsolete: true
Attachment #8583918 -
Flags: review?(honzab.moz)
Attachment #8584021 -
Flags: review?(honzab.moz)
Updated•10 years ago
|
Attachment #8584021 -
Flags: review?(honzab.moz) → review+
| Assignee | ||
Comment 3•10 years ago
|
||
Comment 4•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox40:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•