[
https://issues.apache.org/jira/browse/CASSANDRA-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098998#comment-13098998
]
Jonathan Ellis commented on CASSANDRA-3141:
-------------------------------------------
It does feel a little like premature optimization to me, in the absence of
profiler data showing this is a major expense. When I've looked at similar
profiling before, the actual serialization was much more of a bottleneck than
serializedSize.
> SSTableSimpleUnsortedWriter call to ColumnFamily.serializedSize iterate
> through the whole columns
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3141
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3141
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.3
> Reporter: Benoit Perroud
> Priority: Minor
> Fix For: 0.8.6
>
> Attachments: CachedSizeCF.patch
>
>
> Every time newRow is called, serializedSize iterate through all the columns
> to compute the size.
> Once 1'000'000 columns exist in the CF, it becomes painfull to do at every
> iteration the same computation. Caching the size and incrementing when a
> Column is added could be an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
