Use resident bytes for tracking SharedMemory usage
This CL fixes SharedMemoryTracker::OnMemoryDump to use resident bytes instead of virtual mmap-ed size so that memory-infra allocator dumps will show accurate memory usages of shared memory. SharedMemoryTarcker::OnMemoryDump will use CountResidentBytesInSharedMemory, that uses syscalls (e.g. mincore on Linux). Calling those adds 1-2 [ms] in total to create allocation dumps with one renderer, one browser and one gpu process. See the document regarding the experiments of performance: https://docs.google.com/document/d/1pNwUJVarTCZYaBbiZ4LUuRyTGAocCHKicnats20mLSM/edit# Bug: 713768 Change-Id: Ied163094f9adcf4eba1c109f8ac39a1dae6bb6d3 Reviewed-on: https://chromium-review.googlesource.com/582065 Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> Reviewed-by:danakj <danakj@chromium.org> Reviewed-by:
Primiano Tucci <primiano@chromium.org> Reviewed-by:
Siddhartha S <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#490732}
Showing
Please register or sign in to comment