[ https://issues.apache.org/jira/browse/OAK-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated OAK-3893: ------------------------------- Component/s: (was: segmentmk) segment-next > SegmentWriter records cache could use thinner keys > -------------------------------------------------- > > Key: OAK-3893 > URL: https://issues.apache.org/jira/browse/OAK-3893 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-next > Reporter: Alex Parvulescu > Assignee: Alex Parvulescu > Priority: Minor > Attachments: OAK-3893.patch > > > The SegmentWriter keeps a records deduplication cache ('records' map) that > maintains 2 types of mappings: > * template -> recordid > * strings -> recordid > For the first one (template-> recordid) we can come up with a thinner > representation of a template (a hash function that is fast and not very > collision prone) so we don't have to keep a reference to each template object. > Same applies for second one, similar to what is happening in the StringsCache > now, we could keep the string value up to a certain size and beyond that, > hash it and use that for the deduplication map. -- This message was sent by Atlassian JIRA (v6.3.4#6332)