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-3668) Performance of sstableloader is affected in 1.0.x
Date Fri, 27 Jan 2012 05:09:40 GMT

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

Peter Schuller commented on CASSANDRA-3668:
-------------------------------------------

So I am a bit confused by the history of this ticket. Manish, as far as I can tell, your observations
were that the streaming of a single file is slower than 1.0, correct? I.e., you were watching
iostats and CPU usage while a large file was being streamed?

There is definitely merit to supporting concurrent streaming for a given source/target, I'm
not arguing against that. But I am wondering if I am misunderstanding something, because I
don't see where/how it was established that the original problem was due to a lack of concurrency.
Certainly if there is a huge amount of sstables the latency will cause lower average throughput;
but was it established that this is what's happening? With 350 gigs, even with 1000 sstables,
the average sstable should be large enough that it seems unlikely that the major contributor
to poor performance is the waiting period between streams.
                
> Performance of sstableloader is affected in 1.0.x
> -------------------------------------------------
>
>                 Key: CASSANDRA-3668
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3668
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.0.0
>            Reporter: Manish Zope
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: streaming
>             Fix For: 1.1
>
>         Attachments: 0001-Allow-multiple-connection-in-StreamInSession.patch, 0002-Allow-concurrent-stream-in-StreamOutSession.patch,
0003-Add-threads-option-to-sstableloader.patch, 3688-reply_before_closing_writer.txt, sstable-loader
performance.txt
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> One of my colleague had reported the bug regarding the degraded performance of the sstable
generator and sstable loader.
> ISSUE :- https://issues.apache.org/jira/browse/CASSANDRA-3589 
> As stated in above issue generator performance is rectified but performance of the sstableloader
is still an issue.
> 3589 is marked as duplicate of 3618.Both issues shows resolved status.But the problem
with sstableloader still exists.
> So opening other issue so that sstbleloader problem should not go unnoticed.
> FYI : We have tested the generator part with the patch given in 3589.Its Working fine.
> Please let us know if you guys require further inputs from our side.

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