Investigate LevelDB and opportunities for resource improvement / accounting |
|||||||
Issue descriptionFrom postmortum: https://docs.google.com/document/d/1PphqDNEMLueeTtK5OZDN4HtnQ_hrRHEEQXmyr-C8ST0/edit# Find ways for us to either make leveldb more memory efficient or report stats better so we can be more responsible with usage.
,
Apr 18 2017
,
Apr 18 2017
,
May 3 2017
,
May 3 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 14 2018
,
May 15 2018
Marking as fixed - I think we've poked enough at leveldb here to have bugs for things we want now. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dmu...@chromium.org
, Apr 18 2017