New issue
Advanced search Search tips

Issue 688144 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 669108



Sign in to add a comment

Instrument memory usage of net/disk_cache/blockfile/

Project Member Reported by xunji...@chromium.org, Feb 2 2017

Issue description

The general idea is to have a "size_t EstimateMemoryUsage() const" method for every non-trivial class in net/disk_cache/blockfile. The member method should return the size of dynamically allocated memory in bytes (see more info in base/trace_event/memory_usage_estimator.h)


Then the memory usage can be hooked up in net/'s MemoryDumpProvider (see URLRequestContext::OnMemoryDump() or HttpNetworkSession::DumpMemoryStats()). An example to do this can be found crrev.com/2661333002 or b4199f82689fd146d52d8352f4d07bd79d6cfbd6.

 
Do we care about the blockfile cache?  We only use the simple cache on Android, and want to switch to it everywhere, some day.
Cc: pasko@chromium.org ssid@chromium.org
This is filed as a follow-up for [Instrumenting SimpleCache] https://codereview.chromium.org/2661333002/.

The concern brought up by pasko@ and other reviewers is that if we only have a part of codebase instrumented, it might cause confusion. 

But I agree this is of low priority because blockfile is being deprecated.
Status: Archived (was: Untriaged)
Archived due to lack of activity

Sign in to add a comment