Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 9D0B410084 for ; Tue, 9 Apr 2013 11:52:03 +0000 (UTC) Received: (qmail 16648 invoked by uid 500); 9 Apr 2013 11:52:01 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 16490 invoked by uid 500); 9 Apr 2013 11:52:01 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 16470 invoked by uid 99); 9 Apr 2013 11:52:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 11:52:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 11:51:55 +0000 Received: by mail-ve0-f179.google.com with SMTP id cz11so6205679veb.24 for ; Tue, 09 Apr 2013 04:51:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=8Lc39WSPKU7lYTTggBKR17FUXVGwb9rd8ECV2Pnok+g=; b=PY8IVCg78BAzC6ON6bEG5JrPC1Py2O8P9eRn2Ds8yvxe8tJq3pQ9qY/PNJ91CuhPxs jxPuK++LsTHa0XMiTvs/6KU2a8TbAM43vvNRryTc5/UU6sgAnzRzdQIT/e67yqlRjrk0 lkU6Q8h5eps95/ioZBt6MzjJIkwUDz1W+qtNGQ6A19ot+xwdZGwYxr+ByVQQHFrplKH7 A+4EGpkb9Tc0sGGTVd/5EBGB3trOpagOABA0I2hWfjR+0agzoQa68158kgSPKt5kSGPU jWXpuzB+vzFFCIqJ4jyjQ5bKRxY4tUZlnQ8huWu5vu+ctePHdZCF7KIQXkgS5xC21Fhs 2eZw== X-Received: by 10.58.13.10 with SMTP id d10mr3611198vec.2.1365508294317; Tue, 09 Apr 2013 04:51:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.30.20 with HTTP; Tue, 9 Apr 2013 04:51:14 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Tue, 9 Apr 2013 07:51:14 -0400 Message-ID: Subject: Re: Efficient way to use different storage medium To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnQkUlK47i54Bpwb9uxvTSH1Ku9dZGb+r82BTOGMiGdl7icxTXFujdiklmIN82PbUNsq7CF X-Virus-Checked: Checked by ClamAV on apache.org Hi Bing, If you mount all your drives into HDFS, some blocks are going to be on SSD and some on regular drives. So from reads are going to be fast, and some others are going to be slow. On a single machine, I don't think you can specify which table will be on which drive since the blocks are going to be spread over the drives. You will still see some performances improvement since sometime it's the SSD which is going to be used. Also, at some points, your SSD drives might be full before your regular drives. They will removed from valide WRITE destinations, but will still be used as READs. JM 2013/4/9 Bing Jiang : > hi, > > There are some physical machines which each one contains a large ssd(2T) > and general disk(4T), > and we want to build our hdfs and hbase environment. > > If we use all storage(6T) as each machine provides, I want to know whether > it is an efficient way to > make advantage of ssd, or provide different performance for different table > through hdfs or hbase's configuration as application's requirements. > > From my views, different physical storage medium will provide a good chance > to think over hdfs or hbase's infrastructure, so any views from yours will > be nice. > > Regards > > > -- > Bing Jiang > weibo: http://weibo.com/jiangbinglover > BLOG: http://www.binospace.com > National Research Center for Intelligent Computing Systems > Institute of Computing technology > Graduate University of Chinese Academy of Science