Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 12 Dec 2016 17:28:59 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13027223.1481411866000.499939.1481563739237@Atlassian.JIRA>
In-Reply-To: <JIRA.13027223.1481411866000@Atlassian.JIRA>
References: <JIRA.13027223.1481411866000@Atlassian.JIRA> <JIRA.13027223.1481411866862@arcas>
Subject: [jira] [Commented] (DRILL-5123) Write query profile after sending
 final response to client to improve latency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 12 Dec 2016 17:29:01 -0000


    [ https://issues.apache.org/jira/browse/DRILL-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742525#comment-15742525 ] 

ASF GitHub Bot commented on DRILL-5123:
---------------------------------------

GitHub user paul-rogers opened a pull request:

    https://github.com/apache/drill/pull/692

    DRILL-5123: Write query profile after sending final response to client

    Write query profile after sending final response to client to improve latency
    
    In testing a particular query, I used a test setup that does not write
    to the "persistent store", causing query profiles to not be saved. I
    then changed the config to save them (to local disk). This produced
    about a 200ms difference in query run time as perceived by the client.
    
    I then moved writing the query profile after sending the client the
    final message. This resulted in an approximately 100ms savings, as
    perceived by the client, in query run time on short (~3 sec.) queries.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/paul-rogers/drill DRILL-5123

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/692.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #692
    
----
commit eb3f0f675689b3e867e001b6718d068913491c31
Author: Paul Rogers <progers@maprtech.com>
Date:   2016-12-12T17:18:38Z

    DRILL-5123: Write query profile after sending final response to client to improve latency
    
    In testing a particular query, I used a test setup that does not write
    to the "persistent store", causing query profiles to not be saved. I
    then changed the config to save them (to local disk). This produced
    about a 200ms difference in query run time as perceived by the client.
    
    I then moved writing the query profile after sending the client the
    final message. This resulted in an approximately 100ms savings, as
    perceived by the client, in query run time on short (~3 sec.) queries.

----


> Write query profile after sending final response to client to improve latency
> -----------------------------------------------------------------------------
>
>                 Key: DRILL-5123
>                 URL: https://issues.apache.org/jira/browse/DRILL-5123
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Minor
>
> In testing a particular query, I used a test setup that does not write to the "persistent store", causing query profiles to not be saved. I then changed the config to save them (to local disk). This produced about a 200ms difference in query run time as perceived by the client.
> I then moved writing the query profile _after_ sending the client the final message. This resulted in an approximately 100ms savings, as perceived by the client, in query run time on short (~3 sec.) queries.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)