drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5123) Write query profile after sending final response to client to improve latency
Date Sat, 10 Dec 2016 23:24:58 GMT

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

Paul Rogers commented on DRILL-5123:
------------------------------------

Code change:

      -{{queryManager.writeFinalProfile(sex);}}-

        {{initiatingClient.sendResult(responseListener, resultBuilder.build());}}

      *{{queryManager.writeFinalProfile(sex);}}*

The only negative here is that the query will succeed even if the profile write fails. However,
this seems more like a feature than a bug...

> 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)

Mime
View raw message