[ https://issues.apache.org/jira/browse/IGNITE-21887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov updated IGNITE-21887: -------------------------------------- Fix Version/s: 3.0.0-beta2 > Sql. Reuse caller thread if query already prepared > -------------------------------------------------- > > Key: IGNITE-21887 > URL: https://issues.apache.org/jira/browse/IGNITE-21887 > Project: Ignite > Issue Type: Improvement > Components: sql > Reporter: Konstantin Orlov > Assignee: Konstantin Orlov > Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > As of now, processing of the query unconditionally passed to the `sql-exec` > thread. Although such behavior is rather correct, it introduces additional > penalty in terms of increased latency. For short queries, like point lookup, > this latency in fact is longer than the time of operation itself. > To improve latency of short queries, let's reuse caller thread to initialize > query execution. It's important to make sure we are not hijacking caller > thread for long (on every stage of query initialization we either have to use > cached results, or pass the preparation to `sql-exec` thread). -- This message was sent by Atlassian Jira (v8.20.10#820010)