You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2017/03/28 06:16:41 UTC
[jira] [Closed] (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:all-tabpanel ]
Kunal Khatua closed DRILL-5123.
-------------------------------
Verified when testing with short running queries in a concurrent execution test scenario.
> 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
> Labels: ready-to-commit
> Fix For: 1.10.0
>
>
> 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.15#6346)