You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by paul-rogers <gi...@git.apache.org> on 2016/12/12 17:28:13 UTC

[GitHub] drill pull request #692: DRILL-5123: Write query profile after sending final...

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 <pr...@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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] drill issue #692: DRILL-5123: Write query profile after sending final respon...

Posted by ppadma <gi...@git.apache.org>.
Github user ppadma commented on the issue:

    https://github.com/apache/drill/pull/692
  
    +1. LGTM



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] drill issue #692: DRILL-5123: Write query profile after sending final respon...

Posted by paul-rogers <gi...@git.apache.org>.
Github user paul-rogers commented on the issue:

    https://github.com/apache/drill/pull/692
  
    Fixed comment to explain reasoning without reference to prior behavior.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] drill pull request #692: DRILL-5123: Write query profile after sending final...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] drill issue #692: DRILL-5123: Write query profile after sending final respon...

Posted by sudheeshkatkam <gi...@git.apache.org>.
Github user sudheeshkatkam commented on the issue:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---