[
https://issues.apache.org/jira/browse/CASSANDRA-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185499#comment-17185499
]
Caleb Rackliffe commented on CASSANDRA-15393:
---------------------------------------------
bq. I'm inclined to go the other way, and make underlying type information
opaque everywhere except the serializers themselves. There are very few places
where we need to see it, and making it explicit anywhere it doesn't need to be
just makes it more difficult to make changes later on.
I suppose my starting disposition is wondering why we wouldn't _leave_ it
explicit (i.e. as it is now) if the change hurts readability/clarity for the
benefit of future changes we might not actually make (or if we do make them,
might not look exactly the way we imagine they will here).
> Add byte array backed cells
> ---------------------------
>
> Key: CASSANDRA-15393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15393
> Project: Cassandra
> Issue Type: Sub-task
> Components: Local/Compaction
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We currently materialize all values as on heap byte buffers. Byte buffers
> have a fairly high overhead given how frequently they’re used, and on the
> compaction and local read path we don’t do anything that needs them. Use of
> byte buffer methods only happens on the coordinator. Using cells that are
> backed by byte arrays instead in these situations reduces compaction and read
> garbage up to 22% in many cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
