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 E583CE7DA for ; Fri, 21 Dec 2012 12:27:57 +0000 (UTC) Received: (qmail 96639 invoked by uid 500); 21 Dec 2012 12:27:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96581 invoked by uid 500); 21 Dec 2012 12:27:55 -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 96565 invoked by uid 99); 21 Dec 2012 12:27:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2012 12:27:55 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of james.masson@opigram.com designates 209.85.214.45 as permitted sender) Received: from [209.85.214.45] (HELO mail-bk0-f45.google.com) (209.85.214.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2012 12:27:45 +0000 Received: by mail-bk0-f45.google.com with SMTP id jk13so2320632bkc.32 for ; Fri, 21 Dec 2012 04:27:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=QKiWVDejAQvJqdfLr1FCHdrXHhf4tDgrCYkm+PdymDk=; b=CL0ZrmhsUuFb+tn4wSv+QT/iCWBYNIyN/nocTdgFgd4rBav+TLerNt97sclcdgmGZz AiJfO0Me1X8OkFPiGoH+jwwNTR8jbK++KcitphGUhhf1QZjex7ZN8O5SwXqeDjwyGJao j1nK7JAFJd15Dp7kfULHuIXrZc/S0pb6PNel1nOGUADecq5Pde0ryo0uOF7Pvu6FTLGH xTxlJrMR69N7TIOzbQbDkY9/hytzAJv/zJj9DsYKqhyTuv3p++eZ2cUhwnH8EznNi8+3 ykOZsazVYGzn5hy4GbBhFhfpNNVk6xleItMw5qFKtKj7Mk3y6+VK5cklwVWoSk821p8U AbbQ== X-Received: by 10.204.5.211 with SMTP id 19mr6319638bkw.42.1356092845297; Fri, 21 Dec 2012 04:27:25 -0800 (PST) Received: from [10.10.10.8] ([149.241.118.60]) by mx.google.com with ESMTPS id q22sm9817271bkv.16.2012.12.21.04.27.24 (version=SSLv3 cipher=OTHER); Fri, 21 Dec 2012 04:27:24 -0800 (PST) Message-ID: <50D455AB.4060607@opigram.com> Date: Fri, 21 Dec 2012 12:27:23 +0000 From: James Masson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.7) Gecko/20120824 Thunderbird/10.0.7 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Cassandra read throughput with little/no caching. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQldKygLrAF6apWACFgb+XKj7Ab+shDZ70Fi0pVomL+KJ7bPbAqp8pkhRLVlO1sHKRCaNdkn X-Virus-Checked: Checked by ClamAV on apache.org Hi list-users, We have an application that has a relatively unusual access pattern in cassandra 1.1.6 Essentially we read an entire multi hundred megabyte column family sequentially (little chance of a cassandra cache hit), perform some operations on the data, and write the data back to another column family in the same keyspace. We do about 250 writes/sec and 100 reads/sec during this process. Write request latency is about 900 microsecs, read request latency is about 4000 microsecs. * First Question: Do these numbers make sense? read-request latency seems a little high to me, cassandra hasn't had a chance to cache this data, but it's likely in the Linux disk cache, given the sizing of the node/data/jvm. thanks James M