You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Olsson (JIRA)" <ji...@apache.org> on 2016/12/29 10:14:58 UTC

[jira] [Updated] (CASSANDRA-13084) Avoid byte-array copy when key cache is disabled

     [ https://issues.apache.org/jira/browse/CASSANDRA-13084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Olsson updated CASSANDRA-13084:
--------------------------------------
    Attachment: CASSANDRA-13084-3.X.patch
                CASSANDRA-13084-3.0.patch

Attaching patches for 3.0 and 3.X. The 3.X version should apply cleanly to trunk.

Unfortunately I have not been able to run the dtests locally with these patches as I seem to have some issues with my setup.

> Avoid byte-array copy when key cache is disabled
> ------------------------------------------------
>
>                 Key: CASSANDRA-13084
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13084
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Olsson
>            Assignee: Marcus Olsson
>            Priority: Trivial
>         Attachments: CASSANDRA-13084-3.0.patch, CASSANDRA-13084-3.X.patch
>
>
> While profiling a cluster with the key cache disabled some unnecessary heap pressure was observed. It seems that even though the key cache is disabled we still create the *KeyCacheKey* object which uses _ByteBufferUtil.getArray()_ to copy the keys byte array.
> I don't believe it's a big issue but it's still unnecessary when not using the key cache.



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