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 4B45C703E for ; Thu, 3 Nov 2011 17:56:24 +0000 (UTC) Received: (qmail 19232 invoked by uid 500); 3 Nov 2011 17:56:22 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 19203 invoked by uid 500); 3 Nov 2011 17:56:22 -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 19195 invoked by uid 99); 3 Nov 2011 17:56:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 17:56:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 17:56:16 +0000 Received: by eyg24 with SMTP id 24so1607231eyg.31 for ; Thu, 03 Nov 2011 10:55:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=nOGlZa/6VqwQAthm/lH3EpbvjE8ETQOyHjtaxwZgpCQ=; b=WF0MvUr7ZF/OxbqabR4/kyfwqtQTSnW2TKXeB4S6dwbX5aWUlB7shlAMt6caIDMRS2 zmoOjPoz1HeeR7an5HrQHRoGVv8kTAicI7ONfOps14RncfU9BSopALa6V7bpGTmX26gh tPaKokzvD2ipZUfip57e0+RjnYvQ0VrsPHgxU= Received: by 10.213.28.194 with SMTP id n2mr1307366ebc.96.1320342956290; Thu, 03 Nov 2011 10:55:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.102.19 with HTTP; Thu, 3 Nov 2011 10:55:36 -0700 (PDT) In-Reply-To: References: <167836318403381239@unknownmsgid> From: Jonathan Ellis Date: Thu, 3 Nov 2011 12:55:36 -0500 Message-ID: Subject: Re: Cassandra 1.x and proper JNA setup To: user@cassandra.apache.org, m.miklas@gmx.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Relying on that was always a terrible idea because you could easily OOM before it could help. There's no substitute for "don't make the caches too large" in the first place. We're working on https://issues.apache.org/jira/browse/CASSANDRA-3143 to make cache sizing easier. On Thu, Nov 3, 2011 at 3:16 AM, Maciej Miklas w= rote: > According to source code, JNA is being used to call malloc and free. In t= his > case each cached row will be serialized into RAM. > We must be really careful when defining cache size - to large size would > cause out of memory. Previous Cassandra releases has logic that would > decrease cache size if heap is low. > Currently each row will be serialized without any memory limit checks - > assuming that I understood it right. > > Those properties: > =A0=A0 reduce_cache_sizes_at: 0.85 > =A0=A0 reduce_cache_capacity_to: 0.6 > are not used anymore - at least not when JNA is enabled, witch is default > from Cassandra 1.0 > > > On Wed, Nov 2, 2011 at 1:53 PM, Maciej Miklas > wrote: >> >> I've just found, that JNA will be not used from 1.1 release - >> https://issues.apache.org/jira/browse/CASSANDRA-3271 >> I would be also nice to know what was the reason for this decision. >> >> Regards, >> Maciej >> >> On Wed, Nov 2, 2011 at 1:34 PM, Viktor Jevdokimov >> wrote: >>> >>> Up, also interested in answers to questions below. >>> >>> >>> Best regards/ Pagarbiai >>> >>> Viktor Jevdokimov >>> Senior Developer >>> >>> Email: Viktor.Jevdokimov@adform.com >>> Phone: +370 5 212 3063 >>> Fax: +370 5 261 0453 >>> >>> J. Jasinskio 16C, >>> LT-01112 Vilnius, >>> Lithuania >>> >>> >>> >>> Disclaimer: The information contained in this message and attachments i= s >>> intended solely for the attention and use of the named addressee and ma= y be >>> confidential. If you are not the intended recipient, you are reminded t= hat >>> the information remains the property of the sender. You must not use, >>> disclose, distribute, copy, print or rely on this e-mail. If you have >>> received this message in error, please contact the sender immediately a= nd >>> irrevocably delete this message and any copies.-----Original Message---= -- >>> From: Maciej Miklas [mailto:mac.miklas@googlemail.com] >>> Sent: Tuesday, November 01, 2011 11:15 >>> To: user@cassandra.apache.org >>> Subject: Cassandra 1.x and proper JNA setup >>> >>> Hi all, >>> >>> is there any documentation about proper JNA configuration? >>> >>> I do not understand few things: >>> >>> 1) Does JNA use JVM heap settings? >>> >>> 2) Do I need to decrease max heap size while using JNA? >>> >>> 3) How do I limit RAM allocated by JNA? >>> >>> 4) Where can I see / monitor row cache size? >>> >>> 5) I've configured JNA just for test on my dev computer and so far I've >>> noticed serious performance issues (high cpu usage on heavy write load)= , so >>> I must be doing something wrong.... I've just copied JNA jars into >>> Cassandra/lib, without installing any native libs. This should not work= at >>> all, right? >>> >>> Thanks, >>> Maciej >>> >> > > --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com