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 shutyaev@gmail.com designates
 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKmMYa9zMHZe-1q6qv4v+8==8827tbOPBjjBBoirsJNfbj=jmw@mail.gmail.com>
References: 
 <CAGBp8g8o7kd+spdxiht3nRXDYrs0+Jsy8nWMPgQWM_gxh_YbMA@mail.gmail.com>
	<CAC=xA+XqKjASUYBVqU1X9gH9thHR-PgYgWHgdL46_+DpaYVi2g@mail.gmail.com>
	<CAKmMYa9zMHZe-1q6qv4v+8==8827tbOPBjjBBoirsJNfbj=jmw@mail.gmail.com>
Date: Thu, 19 Dec 2013 16:03:58 +0400
Message-ID: 
 <CAGBp8g-2rjAkvXNr5V+hR0jwu0WxcxhD95Xz+f3Hh3BbZnWTbQ@mail.gmail.com>
Subject: Re: cassandra performance problems
From: Alexander Shutyaev <shutyaev@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11c3dba6dc9e0e04ede1f457

--001a11c3dba6dc9e0e04ede1f457
Content-Type: text/plain; charset=UTF-8

Thanks all for your responses. We've downgraded from 2.0.3 to 2.0.0 and
everything became normal.


2013/12/8 Nate McCall <nate@thelastpickle.com>

> If you are really set on using Cassandra as a cache, I would recommend
> disabling durable writes for the keyspace(s)[0]. This will bypass the
> commitlog (the flushing/rotation of which my be a good-sized portion of
> your performance problems given the number of tables).
>
> [0]
> http://www.datastax.com/documentation/cql/3.0/webhelp/index.html#cql/cql_reference/alter_keyspace_r.html
>
>
> On Fri, Dec 6, 2013 at 12:42 PM, J. Ryan Earl <oss@jryanearl.us> wrote:
>
>> On Thu, Dec 5, 2013 at 6:33 AM, Alexander Shutyaev <shutyaev@gmail.com>wrote:
>>
>>> We've plugged it into our production environment as a cache in front of
>>> postgres. Everything worked fine, we even stressed it by explicitly
>>> propagating about 30G (10G/node) data from postgres to cassandra.
>>>
>>
>> If you just want a caching layer, why wouldn't you use Memcached or Redis
>> instead?  Cassandra is designed to be a persist store and not so much
>> designed as caching layer.  If you were replacing your use of Postgres
>> completely, that would be appropriate.
>>
>
>
>
> --
> -----------------
> Nate McCall
> Austin, TX
> @zznate
>
> Co-Founder & Sr. Technical Consultant
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>

--001a11c3dba6dc9e0e04ede1f457
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks all for your responses. We&#39;ve downgraded from 2=
.0.3 to 2.0.0 and everything became normal.=C2=A0</div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">2013/12/8 Nate McCall <span dir=
=3D"ltr">&lt;<a href=3D"mailto:nate@thelastpickle.com" target=3D"_blank">na=
te@thelastpickle.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">If you are really set on us=
ing Cassandra as a cache, I would recommend disabling durable writes for th=
e keyspace(s)[0]. This will bypass the commitlog (the flushing/rotation of =
which my be a good-sized portion of your performance problems given the num=
ber of tables).=C2=A0<div>

<br></div><div>[0]=C2=A0<a href=3D"http://www.datastax.com/documentation/cq=
l/3.0/webhelp/index.html#cql/cql_reference/alter_keyspace_r.html" target=3D=
"_blank">http://www.datastax.com/documentation/cql/3.0/webhelp/index.html#c=
ql/cql_reference/alter_keyspace_r.html</a></div>

</div><div class=3D"gmail_extra"><div><div class=3D"h5"><br><br><div class=
=3D"gmail_quote">On Fri, Dec 6, 2013 at 12:42 PM, J. Ryan Earl <span dir=3D=
"ltr">&lt;<a href=3D"mailto:oss@jryanearl.us" target=3D"_blank">oss@jryanea=
rl.us</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div>On Thu, Dec 5, 2013 at 6:33 AM, Alexander S=
hutyaev <span dir=3D"ltr">&lt;<a href=3D"mailto:shutyaev@gmail.com" target=
=3D"_blank">shutyaev@gmail.com</a>&gt;</span> wrote:<br>


</div><div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>We&#39;ve p=
lugged it into our production environment as a cache in front of postgres. =
Everything worked fine, we even stressed it by explicitly propagating about=
 30G (10G/node) data from postgres to cassandra.</div>


</div></blockquote><div><br></div></div><div>If you just want a caching lay=
er, why wouldn&#39;t you use Memcached or Redis instead? =C2=A0Cassandra is=
 designed to be a persist store and not so much designed as caching layer. =
=C2=A0If you were replacing your use of Postgres completely, that would be =
appropriate.</div>


</div></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span c=
lass=3D"HOEnZb"><font color=3D"#888888">-- <br><div dir=3D"ltr">-----------=
------<br>Nate McCall<br>Austin, TX<br>@zznate<br><br>Co-Founder &amp; Sr. =
Technical Consultant<br>
Apache Cassandra Consulting<br><a href=3D"http://www.thelastpickle.com" tar=
get=3D"_blank">http://www.thelastpickle.com</a></div>

</font></span></div>
</blockquote></div><br></div>

--001a11c3dba6dc9e0e04ede1f457--