You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/05/06 00:13:18 UTC
[jira] [Comment Edited] (CASSANDRA-6861) Optimise our Netty 4
integration
[ https://issues.apache.org/jira/browse/CASSANDRA-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990038#comment-13990038 ]
Ryan McGuire edited comment on CASSANDRA-6861 at 5/5/14 10:12 PM:
------------------------------------------------------------------
http://riptano.github.io/cassandra_performance/graph_v3/graph.html?stats=stats.6861.json
Looks better overall, but I'm running this a second time to see if the downward spike in the read happens again...
was (Author: enigmacurry):
http://riptano.github.io/cassandra_performance/graph_v3/graph.html?stats=stats.6861.json
I'm running this a second time to see if the downward spike in the read happens again...
> Optimise our Netty 4 integration
> --------------------------------
>
> Key: CASSANDRA-6861
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6861
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: T Jake Luciani
> Priority: Minor
> Labels: performance
> Fix For: 2.1 rc1
>
>
> Now we've upgraded to Netty 4, we're generating a lot of garbage that could be avoided, so we should probably stop that. Should be reasonably easy to hook into Netty's pooled buffers, returning them to the pool once a given message is completed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)