cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3589) Degraded performance of sstable-generator api and sstable-loader utility in cassandra 1.0.x
Date Tue, 14 Feb 2012 02:46:59 GMT

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

Peter Schuller commented on CASSANDRA-3589:
-------------------------------------------

I just realized something. I wasn't looking into this but had a separate realization investigating
streaming performance - ever since Cassandra moved to single-pass streaming (CASSANDRA-2677)
streaming easily becomes CPU bound. If the "mpbs" numbers earlier in this ticket (35, 19)
are mega*bytes*, the numbers are well within what you might reasonably expect from being CPU
bound. I have yet to look into how the bulk loader stuff works, but is it possible it's going
through the same path, such that it's spending CPU time re-creating the sstable on reception?

(This may be obvious to folks, I have actually never look at the bulk loader support before.)
                
> Degraded performance of sstable-generator api and sstable-loader utility in cassandra
1.0.x
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3589
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3589
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.0.0
>            Reporter: Samarth Gahire
>            Priority: Minor
>
> we are using Sstable-Generation API and Sstable-Loader utility.As soon as newer version
of cassandra releases I test them for sstable generation and loading for time taken by both
the processes.Till cassandra 0.8.7 there is no significant change in time taken.But in all
cassandra-1.0.x i have seen 3-4 times degraded performance in generation and 2 times degraded
performance in loading.Because of this we are not upgrading the cassandra to latest version
as we are processing some TeraBytes of data everyday time taken is very important.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message