You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/08/16 13:42:00 UTC

[jira] [Updated] (IGNITE-6084) SQL: improve lazy execution threading model

     [ https://issues.apache.org/jira/browse/IGNITE-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-6084:
------------------------------------
    Labels: performance  (was: )

> SQL: improve lazy execution threading model
> -------------------------------------------
>
>                 Key: IGNITE-6084
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6084
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>              Labels: performance
>             Fix For: 2.2
>
>
> Currently "lazy" mode creates new thread for every query. Moreover, messages are queued to query pool first and then re-submitted to target thread. This makes execution of small queries inefficient. 
> We need to do the following:
> 1) Define separate pool for lazy execution
> 2) It's size should be about 4 x cores, due to blocking nature of lazy execution
> 3) Set thread timeouts
> 4) Submit new query execute request to pool's shared queue from {{GridIoManager}} directly
> 5) Submit "next page" requests to directly to proper thread, using [nodeId, queryId, segment] triplet
> 6) Cancel request can be submitted to query pool and re-submitted to appropriate threads afterwards.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)