[
https://issues.apache.org/jira/browse/CASSANDRA-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173518#comment-14173518
]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-8109:
-------------------------------------------------------------
I have made the code changes in the trunk, did a clean compile and it is going
through fine. What are the specific tests I need to run to make sure that the
changes are working? When I ran the complete test suite "ant test", I am seeing
many failures (even before these changes it was like that). How do I proceed,
please advice. Thanks Raj
> Avoid constant boxing in ColumnStats.{Min/Max}Tracker
> -----------------------------------------------------
>
> Key: CASSANDRA-8109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8109
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Rajanarayanan Thottuvaikkatumana
> Priority: Minor
> Labels: lhf
> Fix For: 3.0
>
>
> We use the {{ColumnStats.MinTracker}} and {{ColumnStats.MaxTracker}} to track
> timestamps and deletion times in sstable. Those classes are generics but we
> really ever use them for longs and integers. The consequence is that every
> call to their {{update}} method (called for every cell during sstable write)
> box it's argument (since we don't store the cell timestamps and deletion time
> boxed). That feels like a waste that is easy to fix: we could just make those
> work on longs only for instance and convert back to int at the end when
> that's what we need.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
