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 C9A1110F8E for ; Fri, 4 Apr 2014 18:53:57 +0000 (UTC) Received: (qmail 89238 invoked by uid 500); 4 Apr 2014 18:53:53 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 89199 invoked by uid 500); 4 Apr 2014 18:53:53 -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 89188 invoked by uid 99); 4 Apr 2014 18:53:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2014 18:53:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tyler@datastax.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2014 18:53:48 +0000 Received: by mail-la0-f45.google.com with SMTP id hr17so2781818lab.4 for ; Fri, 04 Apr 2014 11:53:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=zl2vBNozrCcY2XnofyzoIsnNQ6H+FMCCAsptCdqIp+U=; b=N5fQMeSiXDSwiyyzH+bd90QrvdBkf5FvqbYPwJnYkER2g4OjbHm0ccTK+4pl1LQYof Jz9xBH8XFkp5pbdKFahB2SFGe3prkeptrRgtWY2Ra9OYCukkaNcGrYOd5XvM16vjqib3 /50Opn3CnJeJysle1Ve2VKXItxUuEwJ/kJKjHS0096sawPF0RkifdPChPvMb6UNuLZhh Ql55MI1kqGWadajTmykL3AUjusBBlIH+eyb99JVE0+RhGjFuXQ9DGMEW6ZZ8BLXphaL2 6i94p6CXXYG9TpD6ILllu+ehHl2Yuf4pKOsxAZH3n6kN4b5uv5sq+x4I+W7FLdPVH+0N RjCQ== X-Gm-Message-State: ALoCoQmGJmyOnAqC67aeGLypXiR+n/2NynwcukwfaNa/arzOdZ0OX8AGUo/YOEG6RgengTnMLiWK X-Received: by 10.152.116.43 with SMTP id jt11mr2750433lab.41.1396637607114; Fri, 04 Apr 2014 11:53:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.247.44 with HTTP; Fri, 4 Apr 2014 11:53:07 -0700 (PDT) In-Reply-To: References: From: Tyler Hobbs Date: Fri, 4 Apr 2014 13:53:07 -0500 Message-ID: Subject: Re: Read performance in map data type To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c3656873c71104f63c0803 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3656873c71104f63c0803 Content-Type: text/plain; charset=ISO-8859-1 http://www.datastax.com/documentation/developer/java-driver/2.0/java-driver/tracing_t.html On Fri, Apr 4, 2014 at 11:34 AM, Apoorva Gaurav wrote: > > > On Fri, Apr 4, 2014 at 9:37 PM, Tyler Hobbs wrote: > >> >> On Fri, Apr 4, 2014 at 12:41 AM, Apoorva Gaurav < >> apoorva.gaurav@myntra.com> wrote: >> >>> If we store the same data as a json using text data type i.e (studentID >>> int, subjectMarksJson text) we are getting a latency of ~10ms from the same >>> client for even bigger. I understand that json is not the preferred storage >>> for cassandra and will loose various flexibility which a proper tabular >>> approach provides. But such a huge jump in read latency is killer. I'm >>> pastebin-ing the histogram for json storage as well >>> http://pastebin.com/RiW6hMb2. >>> >> >> Can you trace the slow query and paste the results? >> > How can I enable that > >> >> >> >> -- >> Tyler Hobbs >> DataStax >> > > > > -- > Thanks & Regards, > Apoorva > -- Tyler Hobbs DataStax --001a11c3656873c71104f63c0803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <= div class=3D"gmail_extra">

On Fri, Apr 4, 2014 at 11:34 AM, Apoorva= Gaurav <apoorva.gaurav@myntra.com> wrote:


On Fri, Apr 4, 2014 at 9:37 PM, Tyler Hobbs <t= yler@datastax.com> wrote:
=

On Fri, Apr 4, 2014 at 12:41 AM, Apoorv= a Gaurav <apoorva.gaurav@myntra.com> wrote:
If we store the same data = as a json using text data type i.e (studentID int, subjectMarksJson text) w= e are getting a latency of ~10ms from the same client for even bigger. I un= derstand that json is not the preferred storage for cassandra and will loos= e various flexibility which a proper tabular approach provides. But such a = huge jump in read latency is killer. I'm pastebin-ing the histogram for= json storage as well http://pastebin.com/RiW6hMb2.=A0

Can you trace the slow query and paste the res= ults?
How can I enable that=A0
<= br>

-- =
Tyler Hobbs
DataStax



-- =
Thanks & Regards,
Apoorva



--
Tyler Hobbs
DataStax
 --001a11c3656873c71104f63c0803--