Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 71701 invoked from network); 17 Feb 2010 01:19:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2010 01:19:32 -0000 Received: (qmail 88308 invoked by uid 500); 17 Feb 2010 01:19:31 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 88274 invoked by uid 500); 17 Feb 2010 01:19:31 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 88265 invoked by uid 99); 17 Feb 2010 01:19:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 01:19:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 74.125.78.144 as permitted sender) Received: from [74.125.78.144] (HELO ey-out-1920.google.com) (74.125.78.144) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 01:19:23 +0000 Received: by ey-out-1920.google.com with SMTP id 26so1433353eyw.8 for ; Tue, 16 Feb 2010 17:19:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=A4h5JcXEmAWUEV35rzzoqaiGKZdhawvKOB+MRCOlRkE=; b=KzzriBtyAAOfTlr/TTcSmSXsEssvIOwie1CvnAZIo4Qnnl5r5yfMSAf+jfdRBKOO/z EwWh5JVkZDJXj/Sc9YJqEuKB1xfkxsWFcZuKKcmH1yETwJH5nlKYWojFJfFxzAELoVtu dmYnoNOfbGfIrZCeqCMVc2P0CIRI4kxT7Tn+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=CHlvd4fF7t473SQf1QSCaYgPJW2yCVJJKURs2igRkw73YoMp+lu/yGFyOLIuPfQXeT fzpbJR3MQluCXkLS8r8ur5n7S4wNoYPdyrW6FCl6mUN71TcnMWGXJdUVicixdtMjZfW2 +Y7f6W9C7zEPAw9NZTwHGhhIpTi62KpRrkypY= MIME-Version: 1.0 Received: by 10.216.90.202 with SMTP id e52mr1846873wef.150.1266369543099; Tue, 16 Feb 2010 17:19:03 -0800 (PST) In-Reply-To: References: <468b21171001200244n2521e77esa84964946f0eb20b@mail.gmail.com> <005101caaedd$2bb3ce90$831b6bb0$@com> <1NhIrQ-0007Jt-In@mail.eleven.de> <1266345093.617624017@192.168.2.229> From: Jonathan Ellis Date: Tue, 16 Feb 2010 19:18:43 -0600 Message-ID: Subject: Re: Cassandra benchmark shows OK throughput but high read latency (> 100ms)? To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Have you tried increasing KeysCachedFraction? On Tue, Feb 16, 2010 at 6:15 PM, Weijun Li wrote: > Still have high read latency with 50mil records in the 2-node cluster > (replica 2). I restarted both nodes but read latency is still above 60ms = and > disk i/o saturation is high. Tried compact and repair but doesn't help mu= ch. > When I reduced the client threads from 15 to 5 it looks a lot better but > throughput is kind of low. I changed using flushing thread of 16 instead = the > defaulted 8, could that cause the disk saturation issue? > > For benchmark with decent throughput and latency, how many client threads= do > they use? Can anyone share your storage-conf.xml in well-tuned high volum= e > cluster? > > -Weijun > > On Tue, Feb 16, 2010 at 10:31 AM, Stu Hood wrote= : >> >> > After I ran "nodeprobe compact" on node B its read latency went up to >> > 150ms. >> The compaction process can take a while to finish... in 0.5 you need to >> watch the logs to figure out when it has actually finished, and then you >> should start seeing the improvement in read latency. >> >> > Is there any way to utilize all of the heap space to decrease the read >> > latency? >> In 0.5 you can adjust the number of keys that are cached by changing the >> 'KeysCachedFraction' parameter in your config file. In 0.6 you can >> additionally cache rows. You don't want to use up all of the memory on y= our >> box for those caches though: you'll want to leave at least 50% for your = OS's >> disk cache, which will store the full row content. >> >> >> -----Original Message----- >> From: "Weijun Li" >> Sent: Tuesday, February 16, 2010 12:16pm >> To: cassandra-user@incubator.apache.org >> Subject: Re: Cassandra benchmark shows OK throughput but high read laten= cy >> (> 100ms)? >> >> Thanks for for DataFileDirectory trick and I'll give a try. >> >> Just noticed the impact of number of data files: node A has 13 data file= s >> with read latency of 20ms and node B has 27 files with read latency of >> 60ms. >> After I ran "nodeprobe compact" on node B its read latency went up to >> 150ms. >> The read latency of node A became as low as 10ms. Is this normal behavio= r? >> I'm using random partitioner and the hardware/JVM settings are exactly t= he >> same for these two nodes. >> >> Another problem is that Java heap usage is always 900mb out of 6GB? Is >> there >> any way to utilize all of the heap space to decrease the read latency? >> >> -Weijun >> >> On Tue, Feb 16, 2010 at 10:01 AM, Brandon Williams >> wrote: >> >> > On Tue, Feb 16, 2010 at 11:56 AM, Weijun Li wrote= : >> > >> >> One more thoughts about Martin's suggestion: is it possible to put th= e >> >> data files into multiple directories that are located in different >> >> physical >> >> disks? This should help to improve the i/o bottleneck issue. >> >> >> >> >> > Yes, you can already do this, just add more >> > directives >> > pointed at multiple drives. >> > >> > >> >> Has anybody tested the row-caching feature in trunk (shoot for 0.6?)? >> > >> > >> > Row cache and key cache both help tremendously if your read pattern ha= s >> > a >> > decent repeat rate. =A0Completely random io can only be so fast, howev= er. >> > >> > -Brandon >> > >> >> > >