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 roshandawrani@gmail.com
 designates 209.85.161.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAENxBwy_mC_S5FmemBhpemZeeNAbkoZ9cT=aazZfud+DXhrqOA@mail.gmail.com>
References: 
 <CAMXPLPgwD5R7Jz1WUtXSDfsbvUWcNvWoOzb1nKVwOcbJknNyyA@mail.gmail.com>
	<CAENxBwy_mC_S5FmemBhpemZeeNAbkoZ9cT=aazZfud+DXhrqOA@mail.gmail.com>
Date: Fri, 23 Sep 2011 13:29:29 +0530
Message-ID: 
 <CAMXPLPjOkXcYNLewWTNzBXL98rHP9cVzFVa=k64o8H2_4tttzw@mail.gmail.com>
Subject: Re: Performance degradation observed through embedded cassandra
 server - pointers needed
From: Roshan Dawrani <roshandawrani@gmail.com>
To: hector-users@googlegroups.com
Cc: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001517476a72577ec604ad973006

--001517476a72577ec604ad973006
Content-Type: text/plain; charset=ISO-8859-1

Thanks for sharing your inputs, Edward. Some comments inline below:

On Thu, Sep 22, 2011 at 7:31 PM, Edward Capriolo <edlinuxguru@gmail.com>wrote:
>
>
>> 1) Should should try to dig in an determine why the truncate is slower.
> Look for related jira issues on truncation.
>

I should give it a try. I thought I might get some readymade pointers from
people already knowing about 0.7.2 / 0.8.5 differences on whether our
approach to truncate every test has gone even worse due to some changes in
that area.


> Cassandra had some re-entrant code you could fork a JVM each test and use
> the CassandraServiceDataCleaner. (However multiple startups could end up
> causing more overhead then the truncation)
>
> I avoid this problem by using a different column family and or a different
> keyspaces for all my unit tests in a single class. Each class bring up a new
> embedded cluster and uses the data cleaner to sanitize the data directories.
> So essentially I never call truncate.
>

In both these approaches, won't I need to re-build the schema for every test
too? Certainly in the 2nd case, if I end up creating new keyspace or
different column families for each test. I am not sure what I will gain
there in terms of performance. I was hoping data truncation leaving schema
there would be faster than that.

-- 
Roshan
Blog: http://roshandawrani.wordpress.com/
Twitter: @roshandawrani <http://twitter.com/roshandawrani>
Skype: roshandawrani

--001517476a72577ec604ad973006
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks for sharing your inputs, Edward. Some comments inline below:<br><br>=
<div class=3D"gmail_quote">On Thu, Sep 22, 2011 at 7:31 PM, Edward Capriolo=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:edlinuxguru@gmail.com">edlinuxguru=
@gmail.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class=3D"h5"><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div><br></div></blockquote></div></div></div><div>1) Should should t=
ry to dig in an determine why the truncate is slower. Look for related jira=
 issues on truncation.=A0<br>
</div></blockquote><div><br></div><div>I should give it a try. I thought I =
might get some readymade pointers from people already knowing about 0.7.2 /=
 0.8.5 differences on whether our approach to truncate every test has gone =
even worse due to some changes in that area.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div>Cassandra had some re-en=
trant code you could fork a JVM each test and use the CassandraServiceDataC=
leaner. (However multiple startups could end up causing more overhead then =
the truncation)</div>

<div><br></div><div>I avoid this problem by using a different column family=
 and or a different keyspaces for all my unit tests in a single class. Each=
 class bring up a new embedded cluster and uses the data cleaner to sanitiz=
e the data directories. So essentially I never call truncate.</div>
</blockquote><div><br></div><div>In both these approaches, won&#39;t I need=
 to re-build the schema for every test too? Certainly in the 2nd case, if I=
 end up creating new keyspace or different column families for each test. I=
 am not sure what I will gain there in terms of performance. I was hoping d=
ata truncation leaving schema there would be faster than that.</div>
</div><div><br></div>-- <br>Roshan<br>Blog: <a href=3D"http://roshandawrani=
.wordpress.com/" target=3D"_blank">http://roshandawrani.wordpress.com/</a><=
br>Twitter: <a href=3D"http://twitter.com/roshandawrani" target=3D"_blank">=
@roshandawrani</a><br>
Skype: roshandawrani<br><br>

--001517476a72577ec604ad973006--