asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Khurram Faraaz <khfaraa...@gmail.com>
Subject Re: [AsterixDB] execution time metric in the HTTP API
Date Sat, 03 Dec 2016 18:45:13 GMT
Has anyone here tried the Postman REST Client

https://chrome.google.com/webstore/detail/postman-rest-client/fdmmgilgnpjigdojojpjoooidkmcomcm

On Sat, Dec 3, 2016 at 8:17 PM, Thor Martin Abrahamsen <thorma@stud.ntnu.no>
wrote:

> Thanks for your suggestions, Pouria and Till.
>
> Using the «mode=asynchronous-deferred» returned only the handle, 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 «mode» parameter: 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 «mode=asynchronous-deferred» 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’m wrong
> Pouria). Ideally I would like the isolated AsterixDB execution time, and
> don’t consider network delay or client performance. I might try running 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 <tillw@apache.org<mailto:tillw
> @apache.org>>:
>
> Hi,
>
> an alternative to using the client that Pouria suggested would be to add
> "mode=asynchronous-deferred" as an HTTP parameter when talking to the API.
> 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’m 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
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message