You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/10/18 14:39:58 UTC
[jira] [Updated] (OAK-4953) Optimise MutableRecordNumbers
[ https://issues.apache.org/jira/browse/OAK-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated OAK-4953:
-------------------------------
Attachment: OAK-4953.patch
Proposed patch: [^OAK-4953.patch]
> Optimise MutableRecordNumbers
> -----------------------------
>
> Key: OAK-4953
> URL: https://issues.apache.org/jira/browse/OAK-4953
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: performance
> Fix For: Segment Tar 0.0.16
>
> Attachments: OAK-4953.patch
>
>
> {{MutableRecordNumbers}} is based on a map. This turns to be expensive as the items in the map are accessed very frequently. I would like to look into way of optimising this using a linear storage model instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)