Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4255318C7A for ; Mon, 14 Sep 2015 12:56:20 +0000 (UTC) Received: (qmail 28870 invoked by uid 500); 14 Sep 2015 12:55:45 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 28839 invoked by uid 500); 14 Sep 2015 12:55:45 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 28738 invoked by uid 99); 14 Sep 2015 12:55:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2015 12:55:45 +0000 Date: Mon, 14 Sep 2015 12:55:45 +0000 (UTC) From: "T Jake Luciani (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-10309) Avoid always looking up column type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] T Jake Luciani updated CASSANDRA-10309: --------------------------------------- Issue Type: Improvement (was: Bug) > Avoid always looking up column type > ----------------------------------- > > Key: CASSANDRA-10309 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10309 > Project: Cassandra > Issue Type: Improvement > Reporter: T Jake Luciani > Priority: Minor > Fix For: 3.x > > > Doing some read profiling I noticed we always seem to look up the type of a column from the schema metadata when we have the type already in the column class. > This one simple change to SerializationHeader improves read performance non-trivially. > https://github.com/tjake/cassandra/commit/69b94c389b3f36aa035ac4619fd22d1f62ea80b2 > http://cstar.datastax.com/graph?stats=3fb1ced4-58c7-11e5-9faf-42010af0688f&metric=op_rate&operation=2_read&smoothing=1&show_aggregates=true&xmin=0&xmax=357.94&ymin=0&ymax=157416.6 > I assume we are looking this up to deal with schema changes. But I'm sure there is a more performant way of doing this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)