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/02/01 08:59:39 UTC

[jira] [Commented] (OAK-3958) Split SegmentWriter records cache into 2: strings and templates

    [ https://issues.apache.org/jira/browse/OAK-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125909#comment-15125909 ] 

Michael Dürig commented on OAK-3958:
------------------------------------

Hmm I see. The higher load factor trades some memory for CPU cycles. Not sure whether this is worth it or even notable. Probably not as the write calls are dominated by IO. I guess we will never know until we benchmark....

> Split SegmentWriter records cache into 2: strings and templates
> ---------------------------------------------------------------
>
>                 Key: OAK-3958
>                 URL: https://issues.apache.org/jira/browse/OAK-3958
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>             Fix For: 1.3.15
>
>         Attachments: OAK-3958.patch
>
>
> I think it makes sense to split the 2 caches apart, from what I've seen the ratio is very unbalanced (10 strings to 1 template), so keeping the 2 together might hurt the template cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)