Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 2 Sep 2011 11:14:09 +0000 (UTC)
From: "Benoit Perroud (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <57353684.10136.1314962049847.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2030975916.9977.1314954970121.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-3122) SSTableSimpleUnsortedWriter take
 long time when inserting big rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Perroud updated CASSANDRA-3122:
--------------------------------------

    Attachment: SSTableSimpleUnsortedWriter-v2.patch

Version 2 using getEstimatedColumnCount

> SSTableSimpleUnsortedWriter take long time when inserting big rows
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-3122
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3122
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8.3
>            Reporter: Benoit Perroud
>            Priority: Minor
>         Attachments: SSTableSimpleUnsortedWriter-v2.patch, SSTableSimpleUnsortedWriter.patch
>
>
> In SSTableSimpleUnsortedWriter, when dealing with rows having a lot of columns, if we call newRow several times (to flush data as soon as possible), the time taken by the newRow() call is increasing non linearly. This is because when newRow is called, we merge the size increasing existing CF with the new one.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira