Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of tsaloranta@gmail.com designates
 74.125.83.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=RdRRkMNO9eLTrukyhEi9GKdBD1a8EhWv5A20/2jfvt+UjMGJ8zXKUdFEmV6ExiIX3e
         Jxd6pv7oVdGGlYS04FPYOEd4XqHtUaW9LGX8QWO5B9yi/8rqslrKiL38I9+y8Ku4cOIO
         68fXTWEsr3XxlmZCIUQc6sacYNA11nRHgpD7A=
MIME-Version: 1.0
In-Reply-To: <4BA38CD1.6070808@simpletags.org>
References: <4BA38CD1.6070808@simpletags.org>
Date: Fri, 19 Mar 2010 10:52:13 -0700
Message-ID: <5f7770581003191052w2cd3c765u91ca55b61775e045@mail.gmail.com>
Subject: Re: Startup issue when big data in.
From: Tatu Saloranta <tsaloranta@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Mar 19, 2010 at 7:40 AM, Marcin <marcin@simpletags.org> wrote:
> Hi guys,
>
> is there a way to avoid compacting, flushing and all of this thing on
> startup and perform it while node is running ?
>
> It takes a lot of on startup.

One sort of related question: given that order of insertions has huge
effects on some stores, like BDB (where inserting in key order is 10x
faster than arbitrary order), would insertion order possibly have
significant effect on Cassandra as well if using such stores? I bring
this up because what we found out when creating local bdbs was that
doing disk-sort before inserting big data sets allowed radically
faster creation of these (read-only) databases.

-+ Tatu +-