[
https://issues.apache.org/jira/browse/CASSANDRA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926403#action_12926403
]
Stu Hood commented on CASSANDRA-1651:
-------------------------------------
> As for string interning(1255)
That ticket doesn't say anything about strings.
I mentioned it here because if a key/name was going to live in memory for a
while, we would intern it, which would give us a clear boundary on which to
perform the ByteBuffer copy you mention. The slabs would still be used to
perform the initial interning lookup, and we would still need an explicit
copies for cached values.
> Maybe we should just disable it where the row cache is enabled
Note that this problem applies to the key-cache as well.
> Improve read performance by using byte array slabs
> --------------------------------------------------
>
> Key: CASSANDRA-1651
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1651
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1651_v1.txt
>
>
> Now that the code has switched to byte buffers internally, it should be
> possible to improve read performance by reducing the number of byte array
> allocations.
> This patch accomplishes this by and re-using sections of a larger byte array
> slab.
> I've benchmarked it locally and seen a slight improvement on reads, a larger
> scale benchmark should be performed.
> Also the size of a slab can be configured in cassandra.yaml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
