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 92234200BD2 for ; Sat, 3 Dec 2016 19:45:26 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 910D7160B16; Sat, 3 Dec 2016 18:45:26 +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 D9CAF160B0F for ; Sat, 3 Dec 2016 19:45:25 +0100 (CET) Received: (qmail 84911 invoked by uid 500); 3 Dec 2016 18:45:25 -0000 Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list dev@asterixdb.apache.org Received: (qmail 84894 invoked by uid 99); 3 Dec 2016 18:45:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Dec 2016 18:45:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4D7BA1817A2 for ; Sat, 3 Dec 2016 18:45:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.13 X-Spam-Level: ** X-Spam-Status: No, score=2.13 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id IatkPEyf822a for ; Sat, 3 Dec 2016 18:45:22 +0000 (UTC) Received: from mail-yb0-f180.google.com (mail-yb0-f180.google.com [209.85.213.180]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 3803E5F4A9 for ; Sat, 3 Dec 2016 18:45:22 +0000 (UTC) Received: by mail-yb0-f180.google.com with SMTP id v78so47866398ybe.3 for ; Sat, 03 Dec 2016 10:45:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=vvcpJbKd+1gbOpX3yZkuEALKi6NoU5WCR0BVkVk8e0A=; b=JJ/t7afVTuih9WNsRCiGZL0I3fGSfNcLdckdM60Ti7mGKvEVz2rju77rn7cMumQvJ8 3Ktl4vEVv4mCutRFdZUpuZGmicym0ffCiiylli4ptvnEgKdgsXwtmtMQM1yYwvke4B7W H32RORAury13Ys3LHw2CDekNC9UBkTQ9WcFg8X9sG8klP0nj3FLQG/S0wxIl2Qdla8w3 HLyORTf6BzfhLErQjB/hmM5n5NyVmybM/uEVL/e2COiFp72E2Dd9D0HO0UmBoUjqE5ij GceDN3GxlBVekgJPKqlZZXMvHlDN6NbsrQ0TrH2mjfvxPTXbdM1RJHH+luKIsV1CTamG rE9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=vvcpJbKd+1gbOpX3yZkuEALKi6NoU5WCR0BVkVk8e0A=; b=KlxYB/gaLi25DpVAS229qth/mUl8XlrBK4fLvWULxGUbqGvdSfdbsU6OLu+7YvnRlh pm+TDeKuPWWAgmbzeJP8m3zB+uJjFaScUOYfyyn2rEQCiYCxnUagTgPjE/xavD5MKAAS HTw17QHjshlKI39GVDaO56bWtGvmE8TV9cta+uHoaAwgGkDdPWUpuRTdm8ybrI3Ffmq8 Ya2BNgmbMoa3z1jXS8Xy4Yb0ap8TRo0+/vcgHRxDEhMdr2x6FtMFgeykj4oHWXx/2HfY nobMiSGbVlyfWvkx/wAJdH0BKle/RLD4/XjyAn0IOSSdKkGU/DdgaMRll0PXnHanvmBW jovg== X-Gm-Message-State: AKaTC02WEJaZj42TSlIeixS5oeMSPDshWphFqVwqo3UHjMCBg5QBGitcZMfbu8amYcQsdP4IVW/P06bFemcZkA== X-Received: by 10.37.173.78 with SMTP id l14mr20891898ybe.66.1480790713470; Sat, 03 Dec 2016 10:45:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.13.255.70 with HTTP; Sat, 3 Dec 2016 10:45:13 -0800 (PST) In-Reply-To: <6B0A8058-688A-4AE6-BDF0-F8BCB2410ECB@stud.ntnu.no> References: <2D54DF1B-65A3-4AC9-B503-275932E11DD5@stud.ntnu.no> <7B178564-0D18-4F7E-93C1-62ABC2E3AA6F@apache.org> <6B0A8058-688A-4AE6-BDF0-F8BCB2410ECB@stud.ntnu.no> From: Khurram Faraaz Date: Sun, 4 Dec 2016 00:15:13 +0530 Message-ID: Subject: Re: [AsterixDB] execution time metric in the HTTP API To: dev@asterixdb.apache.org Content-Type: multipart/alternative; boundary=f403045eb12c76ac290542c574ad archived-at: Sat, 03 Dec 2016 18:45:26 -0000 --f403045eb12c76ac290542c574ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Has anyone here tried the Postman REST Client https://chrome.google.com/webstore/detail/postman-rest-client/fdmmgilgnpjig= dojojpjoooidkmcomcm On Sat, Dec 3, 2016 at 8:17 PM, Thor Martin Abrahamsen wrote: > Thanks for your suggestions, Pouria and Till. > > Using the =C2=ABmode=3Dasynchronous-deferred=C2=BB returned only the hand= le, just as I > wanted. But I am not getting any metrics with the response. Just the > handle. The same goes for the request without the =C2=ABmode=C2=BB parame= ter: I only > get the results, not any metrics. Is there a way to get metrics with the > API response? Or is it possible to use =C2=ABmode=3Dasynchronous-deferred= =C2=BB in the > web interface? > > The asterixClient worked perfectly, but the execution time returned is > calculated in the client, not by AsterixDB (please correct me if I=E2=80= =99m wrong > Pouria). Ideally I would like the isolated AsterixDB execution time, and > don=E2=80=99t consider network delay or client performance. I might try r= unning the > client on the same node as the CC :) > > > > Best regards > Thor Martin Abrahamsen > Student @ NTNU > Tlf. +47 470 78 713 > > 2. des. 2016 kl. 20.45 skrev Till Westmann @apache.org>>: > > Hi, > > an alternative to using the client that Pouria suggested would be to add > "mode=3Dasynchronous-deferred" as an HTTP parameter when talking to the A= PI. > In > that case the query should be evaluated completely and an HTTP response > should > come back - however without the result. Instead the response should > contain a > handle where you could pick up the query result (which you could choose > not to > do). > I'm using "should" a lot, as I haven't used this feature for a while, and > so my > recollection of what it does might be buggy or outdated. > > Cheers, > Till > > On 2 Dec 2016, at 11:16, Pouria Pirzadeh wrote: > > You may find the following client useful. > It works against the HTTP, runs query workload for one or more iterations > and dumps the response time per query/iteration in a stats file. > > https://github.com/pouriapirz/asterixClient > > Pouria > > On Fri, Dec 2, 2016 at 10:45 AM, Thor Martin Abrahamsen < > thorma@stud.ntnu.no > wrote: > > Hi, > > Is it possible to get the execution time metric in the HTTP API? > > I=E2=80=99m running some queries and are interested in the execution time= . In the > web interface the duration is printed below the results, but I want the > queries to execute without printing the results. Either in the web > interface, or through the API. The specific query is iterating through a > dataset and applying a library function on each record. > > I am working on a student project together with Heri. > > > Mvh. > Thor Martin Abrahamsen > Student @ NTNU > Tlf. +47 470 78 713 > > > --f403045eb12c76ac290542c574ad--