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 A69157B8 for ; Tue, 19 Apr 2011 01:42:29 +0000 (UTC) Received: (qmail 1614 invoked by uid 500); 19 Apr 2011 00:40:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1594 invoked by uid 500); 19 Apr 2011 00:40:27 -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 1586 invoked by uid 99); 19 Apr 2011 00:40:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 00:40:27 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chris.burroughs@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 00:40:22 +0000 Received: by vws12 with SMTP id 12so4935348vws.31 for ; Mon, 18 Apr 2011 17:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=G2ls+rcVICHu6KRl1n6YFCbDKDv98UiEopBWMpHqItQ=; b=cM/SF5fXaUXetw47SZ7rptOjiRkJKRsWEK4RRTgM4j48U4UrnLk2bHr69mQ4XE9MYo T4XoQZ/plWcyN0UEGQNiTmB6q87iPkTK04r57tlrzX2QjjH2s5z+tsIHowqFXuTWUVsW 7IJvQGJ702AoHSiCfnafQJFE8cZc091b2J7nE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=dCNO9Sa861inT1jme6usrCmHPYD71AUNxZpcCy+8YoqmoMnFPv9m+jCtcCcvxf2FY5 hiQ2xqaXMrpS8EjqUnv/1lNdrhi83VbJDqaFAl9rzql6rAdwbTKC071QL3gC/RaGICz6 ipGuwQmEjKZjGqhIEJsmw2R6BGv6BXPjZ4WBM= Received: by 10.52.94.229 with SMTP id df5mr2802600vdb.288.1303173601327; Mon, 18 Apr 2011 17:40:01 -0700 (PDT) Received: from [10.10.53.15] (cl-pat-tr.clearspring.com [8.18.54.254]) by mx.google.com with ESMTPS id h23sm3563731vbz.9.2011.04.18.17.39.59 (version=SSLv3 cipher=OTHER); Mon, 18 Apr 2011 17:40:00 -0700 (PDT) Message-ID: <4DACD9DD.7060309@gmail.com> Date: Mon, 18 Apr 2011 20:39:57 -0400 From: Chris Burroughs User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: flashcache experimentation Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit https://github.com/facebook/flashcache/ "FlashCache is a general purpose writeback block cache for Linux." We have a case where: - Access to data is not uniformly random (let's say Zipfian). - The "hot" set > RAM. - Size of disk is such that buying enough SSDs, fast drives, multiple drives, etc would be undesirable. This seems like a good case for flashcache. However, as far as I can tell from searching no one has tried this and posted any results. I was wondering if anyone has tried flashcache in a similar situation with Cassandra and if so how the experience went.