Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8597EDEA for ; Tue, 12 Mar 2013 06:12:08 +0000 (UTC) Received: (qmail 9972 invoked by uid 500); 12 Mar 2013 06:12:06 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 9763 invoked by uid 500); 12 Mar 2013 06:12:05 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 9752 invoked by uid 99); 12 Mar 2013 06:12:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 06:12:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a46.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 06:12:01 +0000 Received: from homiemail-a46.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a46.g.dreamhost.com (Postfix) with ESMTP id 1074C3E405B for ; Mon, 11 Mar 2013 23:11:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=TrO+AXeDVX47Q25lYXPNqAQeI+ A=; b=CcaCqJOpUJ1JhuXWiTDFE2a10K58CQ/OJmNw9LZYCN/ciwMEVaqId9X5IN 2UrcxFR1opm8KFZ2yn2+r82YEmuPZGzQS/uK4sJxJvP4x8bdrZYDw6Px8PJUHETq AcxwgeOEtrbgfGM/4Ec4WXfWnoqHMaR6jweB2/6ORK3NDiG58= Received: from [192.168.168.131] (c-98-234-52-29.hsd1.ca.comcast.net [98.234.52.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a46.g.dreamhost.com (Postfix) with ESMTPSA id E20363E4057 for ; Mon, 11 Mar 2013 23:11:40 -0700 (PDT) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_8B0CDF28-3442-4ECD-9819-C4D901E62A86" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Row cache off-heap ? Date: Mon, 11 Mar 2013 23:11:40 -0700 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_8B0CDF28-3442-4ECD-9819-C4D901E62A86 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 What version are you using? Sounds like you have configured it correctly. Did you restart the node = after changing the row_cache_size_in_mb ? The changes in GC activity are not huge and may not be due to cache = activity. Have they continued after you enabled the row cache? What is the output from nodetool info? Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 11/03/2013, at 5:30 AM, S=E1vio Teles = wrote: > I have the same problem!=20 >=20 > 2013/3/11 Alain RODRIGUEZ > I can add that I have JNA corectly loaded, from the logs: "JNA = mlockall successful" >=20 >=20 > 2013/3/11 Alain RODRIGUEZ > Any clue on this ? >=20 > Row cache well configured could avoid us a lot of disk read, and IO is = definitely our bottleneck... If someone could explain why the row cache = has so much impact on my JVM and how to avoid it, it would be = appreciated :). >=20 >=20 > 2013/3/8 Alain RODRIGUEZ > Hi, >=20 > We have some issue having a high read throughput. I wanted to = alleviate things by turning the row cache ON. >=20 > I set the row cache to 200 on one node and enable caching 'ALL' on the = 3 most read CF. There is the effect this operation had on my JVM: = http://img692.imageshack.us/img692/4171/datastaxopscenterr.png >=20 > It looks like the row cache was somehow stored in-heap. I looked at my = cassandra.yaml and I have the following configuration: = row_cache_provider: SerializingCacheProvider (which should be enough to = store row cache off-heap as described above in this file: = "SerializingCacheProvider serialises the contents of the row and stores = it in native memory, i.e., off the JVM Heap") >=20 > What's wrong ? >=20 >=20 >=20 >=20 >=20 > --=20 > Atenciosamente, > S=E1vio S. Teles de Oliveira > voice: +55 62 9136 6996 > http://br.linkedin.com/in/savioteles > Mestrando em Ci=EAncias da Computa=E7=E3o - UFG=20 > Arquiteto de Software > Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG --Apple-Mail=_8B0CDF28-3442-4ECD-9819-C4D901E62A86 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
What version are you = using?

Sounds like you have configured it correctly. = Did you restart the node after changing the row_cache_size_in_mb = ?
The changes in GC activity are not huge and may not be due to = cache activity. Have they continued after you enabled the row = cache?

What is the output from nodetool = info?

Cheers

http://www.thelastpickle.com

On 11/03/2013, at 5:30 AM, S=E1vio Teles <savio.teles@lupa.inf.ufg.br> wrote:

I have the same problem!

2013/3/11 Alain RODRIGUEZ <arodrime@gmail.com>
I can add that I have JNA corectly loaded, from the = logs: "JNA mlockall successful"


2013/3/11 Alain RODRIGUEZ <arodrime@gmail.com>
Any clue on this ?

Row cache = well configured could avoid us a lot of disk read, and IO = is definitely our bottleneck... If someone could explain why = the row cache has so much impact on my JVM and how to avoid it, it would = be appreciated :).


2013/3/8 Alain RODRIGUEZ <arodrime@gmail.com>
Hi,

We have some issue = having a high read throughput. I wanted to alleviate things by turning = the row cache ON.

I set the row cache to 200 on = one node and enable caching 'ALL' on the 3 most read CF. There is the = effect this operation had on my JVM: http://img692.imageshack.us/img692/4171/datastaxopscente= rr.png

It looks like the row cache was somehow stored = in-heap. I looked at my cassandra.yaml and I have the following = configuration: row_cache_provider: SerializingCacheProvider (which = should be enough to store row cache off-heap as described above in this = file: "SerializingCacheProvider serialises the contents of the row and = stores it in native memory, i.e., off the JVM Heap")

What's wrong ?





--
Atenciosamente,
S=E1vio S. Teles de = Oliveira
voice: +55 62 9136 6996
http://br.linkedin.com/in/savioteles
Mestrando em Ci=EAncias da Computa=E7=E3o - UFG
Arquiteto de = Software
Laboratory for Ubiquitous and Pervasive = Applications (LUPA) - UFG

= --Apple-Mail=_8B0CDF28-3442-4ECD-9819-C4D901E62A86--