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

Sam Tunnicliffe commented on CASSANDRA-11593:
---------------------------------------------

+1 on the 3.0 patch too.

> 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)

Reply via email to