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] [Updated] (CASSANDRA-11593) getFunctions methods produce too much garbage
Date Mon, 02 May 2016 12:24:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Lerer updated CASSANDRA-11593:
---------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.x)
                   3.0.6
                   3.6
           Status: Resolved  (was: Ready to Commit)

Committed into 3.0 at 89464ead48278f8e3ecfeaeaf9571714978b4f72 and merged into trunk.

> 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.6, 3.0.6
>
>         Attachments: 11593-3.0.txt, 11593-trunk.txt
>
>
> 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