Return-Path: 
 <user-return-7515-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: (qmail 29320 invoked from network); 13 Jul 2010 02:01:53 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 13 Jul 2010 02:01:53 -0000
Received: (qmail 47070 invoked by uid 500); 13 Jul 2010 02:01:52 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 47019 invoked by uid 500); 13 Jul 2010 02:01:51 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 47011 invoked by uid 99); 13 Jul 2010 02:01:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 02:01:51 +0000
X-ASF-Spam-Status: No, hits=2.9 required=10.0
	tests=HTML_MESSAGE,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com)
 (209.85.161.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 02:01:44 +0000
Received: by gxk3 with SMTP id 3so3307864gxk.31
        for <user@cassandra.apache.org>; Mon, 12 Jul 2010 19:00:33 -0700 (PDT)
Received: by 10.150.31.15 with SMTP id e15mr3419637ybe.216.1278986432950;
        Mon, 12 Jul 2010 19:00:32 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com
 [209.85.161.172])
        by mx.google.com with ESMTPS id m13sm4173485ybn.9.2010.07.12.19.00.32
        (version=SSLv3 cipher=RC4-MD5);
        Mon, 12 Jul 2010 19:00:32 -0700 (PDT)
Received: by gxk3 with SMTP id 3so3307854gxk.31
        for <user@cassandra.apache.org>; Mon, 12 Jul 2010 19:00:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.170.2 with SMTP id s2mr5911931ybe.305.1278986431815; Mon,
	12 Jul 2010 19:00:31 -0700 (PDT)
Received: by 10.151.13.21 with HTTP; Mon, 12 Jul 2010 19:00:31 -0700 (PDT)
Date: Mon, 12 Jul 2010 21:00:31 -0500
Message-ID: <AANLkTik9teCX5kopjT_qJqEIFL1box7RaWO91yS_NNFj@mail.gmail.com>
Subject: concurrent reads
From: Lee Parker <lee@socialagency.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=000e0cd39c7af0e4c3048b3b3b79
X-Virus-Checked: Checked by ClamAV on apache.org

--000e0cd39c7af0e4c3048b3b3b79
Content-Type: text/plain; charset=ISO-8859-1

Has anyone experimented with different settings for concurrent reads?  I
have set our servers to 4 ( 2 per processor core ).  I have noticed that
occasionally, our pending reads will get backed up and our servers don't
appear to be under too much load.  In fact, most of the load appears to be
from GC.  Is 3 per processor core too much?  Does it matter if it is an AMC
vs Intel processor?  How does processor clock speed or cache play into this
setting?

Lee Parker

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

Has anyone experimented with different settings for concurrent reads? =A0I =
have set our servers to 4 ( 2 per processor core ). =A0I have noticed that =
occasionally, our pending reads will get backed up and our servers don&#39;=
t appear to be under too much load. =A0In fact, most of the load appears to=
 be from GC. =A0Is 3 per processor core too much? =A0Does it matter if it i=
s an AMC vs Intel processor? =A0How does processor clock speed or cache pla=
y into this setting?<br>
<div title=3D"signature"><p>Lee Parker</p></div>

--000e0cd39c7af0e4c3048b3b3b79--