New issue
Advanced search Search tips

Issue 716124 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Feature


Show other hotlists

Hotlists containing this issue:
IDB-Scaling


Sign in to add a comment

Investigate & possibly implement LevelDB key reading optimizations

Project Member Reported by dmu...@chromium.org, Apr 27 2017

Issue description

Key prefix compression is great, but if we have really large keys the current implementation has a lot of memory churn.

Opportunities:
 * Create ability to not copy key into std::string if not shared with previous key - introduces a branch but more memory efficient.
 * Test when writing if new key size is > X bytes, then don't do prefix compression (probably do size - shared size) to prevent string copy above. Thinking about MB sized keys
 

Comment 1 by dmu...@chromium.org, Apr 27 2017

Labels: -Type-Bug Type-Feature
Project Member

Comment 2 by sheriffbot@chromium.org, Apr 30 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 3 by dmu...@chromium.org, Apr 30 2018

Status: Available (was: Untriaged)

Sign in to add a comment