cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7349) Use Native Frame in CommitLog
Date Wed, 04 Jun 2014 01:24:01 GMT

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

Jonathan Ellis commented on CASSANDRA-7349:
-------------------------------------------

Doesn't this only help if the coordinator is a replica?  What if it's a big frame, does that
cause extra memory pressure?

Historical note: in the Dark Ages, we used to do this at (IIRC) the MS level, where we'd copy
the bytes into a BB and just blast that to the log instead.  Turned out that creating the
BB was more expensive than just re-serializing them, though.  Should be able to find this
in the CLSegment or ITC class history.

> Use Native Frame in CommitLog
> -----------------------------
>
>                 Key: CASSANDRA-7349
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7349
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: T Jake Luciani
>              Labels: performance
>             Fix For: 3.0
>
>
> We currently read mutations off the wire then re-serialize them to the commit log.  In
the case of the Native protocol we have the native Frame available in the mutation we should
be able to special case this and use it in the commit log.  I would expect a decent performance
boost.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message