[
https://issues.apache.org/jira/browse/CASSANDRA-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649189#comment-14649189
]
Sylvain Lebresne commented on CASSANDRA-9940:
---------------------------------------------
If it's just the serialization-deserialization cost we want to avoid, then it
should be trivial to put everything in an {{ArrayBackedPartition}} (would be
nice to benchmark it for good measure though). Avoiding pulling it all in
memory is harder though, not only due to {{OpOrder}} reasons pointed out by
Benedict, but also because in some case we need to both return the result and
digest it. Both are likely solvable in some way, but will most probably require
refactor that goes way beyond just {{ReadResponse}}. So I'd personally stick to
just pulling it all in a {{Parttion}} object for now (instead of
serializing-deserializing), but that's just my 2 cents.
> ReadResponse serializes and then deserializes local responses
> -------------------------------------------------------------
>
> Key: CASSANDRA-9940
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9940
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
>
> Noticed this reviewing CASSANDRA-9894. It would be nice to not have to do
> this busy work. Benedict said it wasn't straightforward to avoid because it's
> being done to allow the read op order group to close.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
