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 28D1710CD2 for ; Fri, 19 Dec 2014 20:02:14 +0000 (UTC) Received: (qmail 14881 invoked by uid 500); 19 Dec 2014 20:02:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 14838 invoked by uid 500); 19 Dec 2014 20:02:13 -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 14826 invoked by uid 99); 19 Dec 2014 20:02:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 20:02:13 +0000 Date: Fri, 19 Dec 2014 20:02:13 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8520) Prototype thread per core 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-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253933#comment-14253933 ] Aleksey Yeschenko commented on CASSANDRA-8520: ---------------------------------------------- bq. I mean touches sstables and not memtables, because the majority of reads work is this way. Ideally we would do this test against a new better storage format as well, and certainly we would optimise the read path. Ah. This makes sense. Sorry. And yes, the issue is labeled 3.1 because it's blocked by CASSANDRA-8099. > Prototype thread per core > ------------------------- > > Key: CASSANDRA-8520 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8520 > Project: Cassandra > Issue Type: Task > Components: Core > Reporter: Jonathan Ellis > Labels: performance > Fix For: 3.1 > > > Let's prototype the best possible scenario for how well we can perform with a thread per core design by simplifying everything we can. For instance, > - No HH, no RR, no replication at all > - No MessagingService > - No compaction (so test a workload w/o overwrites) > - No repair > - Just local writes and reads > If we can't get a big win (say at least 2x) with these simplifications then I think we can say that it's not worth it. > If we can get a big win, then we can either refine the prototype to make it more realistic or start working on it in earnest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)