You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2016/12/10 23:37:58 UTC
[jira] [Comment Edited] (DRILL-5123) Write query profile after
sending final response to client to improve latency
[ https://issues.apache.org/jira/browse/DRILL-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738660#comment-15738660 ]
Paul Rogers edited comment on DRILL-5123 at 12/10/16 11:36 PM:
---------------------------------------------------------------
Code change:
-{{queryManager.writeFinalProfile(uex);}}-
{{initiatingClient.sendResult(responseListener, resultBuilder.build());}}
*{{queryManager.writeFinalProfile(uex);}}*
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...
was (Author: paul-rogers):
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)