New issue
Advanced search Search tips

Issue 714384 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Consider using flat_map for TabContentManager maps

Project Member Reported by brettw@chromium.org, Apr 22 2017

Issue description

chrome/browser/android/compositor/tab_content_manager.h has some maps in it for LayerMap and ThumbnailLayerMap.

These sound like they might be small. Currently they're unordered_maps which will be wasting a lot of space for hash tables. I'm changing them to std::map.

But I can't check how big these actually are. If they are small, we should be using a base::flat_map instead.
 
Worth adding a small bit of UMA instrumentation to see their size?

Comment 2 by brettw@chromium.org, May 23 2017

Somebody on Android that understand these can probably do it locally and get a good enough idea.
Labels: android-fe-triaged
Status: Available (was: Untriaged)

Sign in to add a comment