Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CA9F0200C5B for ; Thu, 27 Apr 2017 19:50:40 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C92EB160BA7; Thu, 27 Apr 2017 17:50:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EABEF160B9E for ; Thu, 27 Apr 2017 19:50:39 +0200 (CEST) Received: (qmail 79856 invoked by uid 500); 27 Apr 2017 17:50:39 -0000 Mailing-List: contact user-help@kudu.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@kudu.apache.org Delivered-To: mailing list user@kudu.apache.org Received: (qmail 79846 invoked by uid 99); 27 Apr 2017 17:50:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2017 17:50:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 7CCCD1B0E47 for ; Thu, 27 Apr 2017 17:50:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.389 X-Spam-Level: ** X-Spam-Status: No, score=2.389 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, T_ANY_PILL_PRICE=0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id jbAGFzDEm4bX for ; Thu, 27 Apr 2017 17:50:37 +0000 (UTC) Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 694CF5FB5C for ; Thu, 27 Apr 2017 17:50:37 +0000 (UTC) Received: by mail-it0-f49.google.com with SMTP id x188so18481022itb.0 for ; Thu, 27 Apr 2017 10:50:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=KYK/xclTcLjeYzq0it1EYDiu7jtUhOlBSK/eYep1gbw=; b=LHbBAPAdydiWEgkThcYT1I3ob+CVrsWjL99SMJcLXuIqsF7tUWNQh4p/5x4aZhDRcI BYaHxpLqsBRtbCEXI7j/mbrqCCR2QvKXH3cPhNlZjqq+S1gznd/6fbVXQiHP2DC1spKG b+m2Vc6fHuXOiMuGF51ZwmM+di8fj+8zUpPUJOKardcR6HkVgy2b3entGv3DZdKQdV6Q dMZRfBYfyoSYnIfYDTOK+8P3ZB3K4GH9619ORH+Bu15tlU//CxKTJEH/VJONejeyUMnW zZgXqgNMltoVODuyZPLHDTiTiUcBfVCQ/3kq9AbQhksqZ06SOuNc7kunQ0s2C/IKdbBg 1FWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=KYK/xclTcLjeYzq0it1EYDiu7jtUhOlBSK/eYep1gbw=; b=J1NJK313URxs0EFtWXEm4MPF+DvvoPfwjychEQ1NmU4LIVcsXmcVgvV6hL5A/eg5fK fPYgFDtR0e+uPcPC9lI0FB8fT7rzjfS4yGTRgIu96ZMKonO5BLvPIUOY/uNcU21OGgiv eZikOmcxlrXHS0wgIDQMBMZZK7FvY4QerSfmL5e24c5i3DJmdl9kR41I3RlGqFw19V29 QTh8rwF+d1ci+RpSuGRw9wcnbSvSnBrxDM9fuscBBwaM4OD8O4KlWbwCyfDZpLqeMzFL 8lGmnzEKtoSK20WtY6T+hB6o4m946/v5QM5na4iLULcWfZwti2HXMETASUsJWxEbSRIU gHEA== X-Gm-Message-State: AN3rC/6KVDy5iVEsk9d0IQ1fP4BuPr2/4USLo1vXGngQoi6t1saPR0du ph2Y7I4IVyB+dkdYfReZVv12E9rI186e X-Received: by 10.157.17.139 with SMTP id v11mr3468465otf.197.1493315436723; Thu, 27 Apr 2017 10:50:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.236.161 with HTTP; Thu, 27 Apr 2017 10:50:16 -0700 (PDT) In-Reply-To: References: From: David Alves Date: Thu, 27 Apr 2017 10:50:16 -0700 Message-ID: Subject: Re: Kudu Table Design Question To: user Content-Type: multipart/alternative; boundary=94eb2c1921ea24c666054e2998fd archived-at: Thu, 27 Apr 2017 17:50:41 -0000 --94eb2c1921ea24c666054e2998fd Content-Type: text/plain; charset=UTF-8 The suggestion of 20-30 per tablet is more about the number of available cores than the size of the data. Tools like impala derive parallelism from the number of tablets thus having that count adjusted (but not necessarily equal to) to the core count gives you a good performance tradeoff. Of course this is not a hard limit, the tablet server should be able anything up to 100 reasonably well depending on your hardware. HTH -david On Tue, Apr 25, 2017 at 9:19 PM, Jason Heo wrote: > Hi. > > This email > (and > many other resources) suggests that tserver should have small number of > tablets. > > In the above mail, Dan says that: > > >> something more like 20 or 30 would be ideal depending on hardware.. > >> ... > >> I would aim for tablet size on the order of 50GiB, > > > I'm curious why 20~30 per tserver would be ideal. Does this mean storing > 1TB~1.5TB per tserver is ideal? Could someone please explain this? > > The reason I ask is that I'm currently doing capacity planning. > > Regards, > > Jason > --94eb2c1921ea24c666054e2998fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The suggestion of 20-30 per tablet is more about the numbe= r of available cores than the size of the data.
Tools like impala deriv= e parallelism from the number of tablets thus having that count adjusted (b= ut not necessarily equal to) to the core count gives you a good performance= tradeoff.
Of course this is not a hard limit, the tablet server = should be able anything up to 100 reasonably well depending on your hardwar= e.

HTH
-david

=

On Tue, Apr 25, 2= 017 at 9:19 PM, Jason Heo <jason.heo.sde@gmail.com> wr= ote:
Hi.

<= div>This email=C2=A0(and many other resources) su= ggests that tserver should have small number of tablets.

In the above mail, Dan says that:
>> somethin= g more like 20 or 30 would be ideal depending on hardware..
>> ...=
>> I would aim for tablet size on the order of 50GiB,

I'm curious why 20~30 per tserver would be ideal. = Does this mean storing 1TB~1.5TB per tserver is ideal? Could someone please= explain this?

The reason I ask is that I'm cu= rrently doing capacity planning.

Regards,

Jason

--94eb2c1921ea24c666054e2998fd--