Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9B49E184BD for ; Mon, 16 Nov 2015 16:51:08 +0000 (UTC) Received: (qmail 30678 invoked by uid 500); 16 Nov 2015 16:51:08 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 30634 invoked by uid 500); 16 Nov 2015 16:51:08 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 30622 invoked by uid 99); 16 Nov 2015 16:51:08 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2015 16:51:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 99BE0C6A4E for ; Mon, 16 Nov 2015 16:51:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.213 X-Spam-Level: **** X-Spam-Status: No, score=4.213 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Ykek1ZCx3YWA for ; Mon, 16 Nov 2015 16:50:53 +0000 (UTC) Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com [209.85.160.181]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 7319020C41 for ; Mon, 16 Nov 2015 16:50:53 +0000 (UTC) Received: by ykdv3 with SMTP id v3so249023793ykd.0 for ; Mon, 16 Nov 2015 08:50:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/EM0gYQGXYht+c1kPskkR5Iyq76BxfWawvQ4crYdzjQ=; b=VaZmpZ9X/aqNnFaE6Owi/Kkk6jzMJjMVMke3FJsE2b6cxplOWbKeT9UONGExk7nsYH JITaSjntGDh5NwZlsZczSxrWh9PfUZdLEEoQryIMXOp6HlKai1taixt3ARzZUwZKeGV6 BnfzIvhlqMO1eOTY+KVxvwO888HqXeKVr10fskDRYxzfzpnJv5K9THbWns+Io67MhyFv G5eigmvox84ZHwmS856LgCERKWCF7vzA3IM9D4MNHa7Pv2bOF/xlpB6uVzxtgvsLq2Bf 31IN1V6ZpCmx1uouBY7SuNV7xV1HRxL8uUJFEyP7pX8Xatvvpep+vwMWtI4vSIyA7mjA VhGw== MIME-Version: 1.0 X-Received: by 10.13.221.208 with SMTP id g199mr40615048ywe.225.1447692652546; Mon, 16 Nov 2015 08:50:52 -0800 (PST) Received: by 10.129.157.141 with HTTP; Mon, 16 Nov 2015 08:50:52 -0800 (PST) In-Reply-To: <1447690747868-15571.post@n5.nabble.com> References: <1447688111824-15569.post@n5.nabble.com> <1447690747868-15571.post@n5.nabble.com> Date: Mon, 16 Nov 2015 11:50:52 -0500 Message-ID: Subject: Re: delete rows test result From: William Slacum To: dev Content-Type: multipart/alternative; boundary=94eb2c06e3fa4c933f0524ab3665 --94eb2c06e3fa4c933f0524ab3665 Content-Type: text/plain; charset=UTF-8 "Reading" all of the rows first implies you're bringing back the entire result to a client, which provides you serial access to the data. I think you should re-run test #3 that measures the time it takes to call deleteRows only. I'm emphasizing this because I've worked on projects that could quickly define a range to be deleted without reading any data, and using deleteRows decreased our latency significantly On Mon, Nov 16, 2015 at 11:19 AM, z11373 wrote: > I didn't do that, but I am sure can extrapolate that from Test 1. > > Test 1 is doing: > foreach k/v in scanner's iterator > create a new mutation with that row > call putDelete > > Test 3 is doing > foreach k/v in scanner's iterator > assign the row of first entry to 'first' var > assign the row to a 'last' var > After the loop is done, pass 'first' and 'last' vars to deleteRows. > > So, if I'd extrapolate the time without reading all rows, then we can > subtract result from Test 1 from result from Test 3, i.e. for Table 1 is > 196,597 - 5,702 = 190,895 (this is still way too long) > > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/delete-rows-test-result-tp15569p15571.html > Sent from the Developers mailing list archive at Nabble.com. > --94eb2c06e3fa4c933f0524ab3665--