Open Bug 699410 Opened 13 years ago Updated 2 years ago

Add telemetry for memory used by active disk cache entries

Categories

(Core :: Networking: Cache, defect, P5)

defect

Tracking

()

People

(Reporter: u408661, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-would-take])

Attachments

(1 file)

We would like to know how much memory overhead we have in the disk cache caused by entries that are in use in some way or another (reading, writing, not-yet-deactivated). Not 100% sure WHEN to probe this number, and whether to do the actual memory calculation or just count the number of active entries and extrapolate as best as possible from there.
Please use moz_malloc_usable_size() if you can -- see bug 669409 comment 5.
Attached patch patchSplinter Review
This patch builds on the one for bug 699951, so just requesting feedback for now, but it's in the final form that I'd like it to be in barring any problems.
Attachment #575903 - Flags: feedback?(jduell.mcbugs)
Comment on attachment 575903 [details] [diff] [review] patch Review of attachment 575903 [details] [diff] [review]: ----------------------------------------------------------------- Looks fine to me, but I'm not familiar with the "gather-telemetry" event, so asking Taras to glance at it too.
Attachment #575903 - Flags: feedback?(jduell.mcbugs) → feedback?(tglek)
Comment on attachment 575903 [details] [diff] [review] patch gather-telemetry is an event we fire to give stuff a chance to gather one-off (and possibly async+expensive) telemetry data.
Attachment #575903 - Flags: feedback?(tglek) → feedback+
Reassigning to default owner, 'cause this will all change when we get our new cache, and someone else will likely be more appropriate to do this then.
Assignee: hurley → nobody
Whiteboard: [necko-would-take]
Priority: -- → P5
Blocks: 572459
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: