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 0FD98114E5 for ; Fri, 28 Mar 2014 18:23:24 +0000 (UTC) Received: (qmail 30061 invoked by uid 500); 28 Mar 2014 18:23:23 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 29823 invoked by uid 500); 28 Mar 2014 18:23:22 -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 29319 invoked by uid 99); 28 Mar 2014 18:23:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2014 18:23:20 +0000 Date: Fri, 28 Mar 2014 18:23:20 +0000 (UTC) From: "Benedict (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6890) Remove mmap'ed i/o from read path 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-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951179#comment-13951179 ] Benedict commented on CASSANDRA-6890: ------------------------------------- FTR, with compression enabled it will only use mmapped IO for reading the index file, not the compressed data. I'm not tremendously surprised that we see a drop in throughput vs mmapped files, as we compress 64K chunks, so we have to read a minimum of 64K (+ readahead), and also decompress it for every row we lookup, which in this case is only ~200 bytes. I would expect the performance difference to be smaller for larger rows. Tuning performance for standard IO is trickier for the user, and we don't currently do much to help them. Personally, I am -1 on removing mmapped IO as an option until we have an in-process uncompressed page cache that mitigates these problems. > Remove mmap'ed i/o from read path > --------------------------------- > > Key: CASSANDRA-6890 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6890 > Project: Cassandra > Issue Type: Improvement > Reporter: Joshua McKenzie > Assignee: Joshua McKenzie > Priority: Minor > Fix For: 3.0 > > Attachments: mmap_gc.jpg, mmap_jstat.txt, mmap_perf.txt, nommap_gc.jpg, nommap_jstat.txt > > > Since we actively unmap unreferenced SSTR's and also copy data out of those readers on the read path, the current memory mapped i/o is a lot of complexity for very little payoff. Clean out the mmapp'ed i/o on the read path. -- This message was sent by Atlassian JIRA (v6.2#6252)