Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of benoit@noisette.ch designates
 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1335571187223-7507756.post@n2.nabble.com>
References: <1335571187223-7507756.post@n2.nabble.com>
Date: Sun, 29 Apr 2012 18:49:04 +0200
Message-ID: 
 <CALxZ3YwxRDt4VVrNEvvJV6TD91toYVmTueGD7mL_7--j6iSxLw@mail.gmail.com>
Subject: Re: Building SSTables with SSTableSimpleUnsortedWriter
From: Benoit Perroud <benoit@noisette.ch>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

big buffer size will use more Heap memory at creation of the tables.
Not sure impact on server side, but shouldn't be a big difference. I
personally use 512Mb.


2012/4/28 sj.climber <sj.climber@gmail.com>:
> Can anyone comment on best practices for setting the buffer size used by
> SSTableSimpleUnsortedWriter? =C2=A0I'm presently using 100MB, but for som=
e of the
> larger column families I'm working with, this can result in hundreds of
> SSTables. =C2=A0After streaming to Cassandra via sstableloader, there's a=
 fair
> amount of compaction work to do.
>
> What are the benefits and consequences of going with a higher buffer size=
?
>
> Thanks!
>
> --
> View this message in context: http://cassandra-user-incubator-apache-org.=
3065146.n2.nabble.com/Building-SSTables-with-SSTableSimpleUnsortedWriter-tp=
7507756.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at=
 Nabble.com.


--=20
sent from my Nokia 3210