cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3668) Performance of sstableloader is affected in 1.0.x
Date Thu, 19 Jan 2012 00:22:40 GMT


Yuki Morishita updated CASSANDRA-3668:

    Attachment: 0003-Add-threads-option-to-sstableloader.patch

Attached patches add threads option(-t) to sstableloader. The option allows you to configure
# of threads per destination.

I made patches for trunk because in 1.0 branch streaming socket is one-to-one to incoming
stream session.

I got better throughput with 4 threads, and  observed little impact on target node's cpu and
> Performance of sstableloader is affected in 1.0.x
> -------------------------------------------------
>                 Key: CASSANDRA-3668
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.0.7
>            Reporter: Manish Zope
>            Assignee: Yuki Morishita
>             Fix For: 1.0.8
>         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
>   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 :- 
> 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:!default.jspa
For more information on JIRA, see:


View raw message