cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11593) getFunctions methods produce too much garbage
Date Fri, 29 Apr 2016 12:31:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263984#comment-15263984
] 

Benjamin Lerer commented on CASSANDRA-11593:
--------------------------------------------

I pushed a new patch for 3.0.x.
|[3.0|https://github.com/blerer/cassandra/tree/11593-3.0]|[utest|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11593-3.0-testall/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11593-3.0-dtest/2/]|


> getFunctions methods produce too much garbage
> ---------------------------------------------
>
>                 Key: CASSANDRA-11593
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11593
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>             Fix For: 3.x
>
>
> While profiling an heavy write workload on a single machine, I discover that calls to
{{getFunctions}} were producing a lot of garbage.
> Internally, the getFunctions method use {{Iterators}} or {{Iterables}} functions that
creates new immutable collections at each level.
> As {{getFunctions}} is called for each SELECT, INSERT, UPDATE or DELETE through the {{checkAccess}}
method the impact is not neglectable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message