ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9171) Use lazy mode with results pre-fetch
Date Fri, 01 Feb 2019 08:09:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758070#comment-16758070

Vladimir Ozerov commented on IGNITE-9171:

[~tledkov-gridgain], I propose to decouple lock for cancel command synchronization from table
locks. If we do not do this, further development of {{KILL}} command will be more difficult
due to subtle dependencies.

> Use lazy mode with results pre-fetch
> ------------------------------------
>                 Key: IGNITE-9171
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9171
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.6
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>            Priority: Critical
>              Labels: sql-stability
>             Fix For: 2.8
> Current implementation of the {{lazy}} mode always starts separate thread for {{MapQueryLazyWorker}}.
It  causes excessive overhead for requests that produces small results set.
> We have to begin execute query at the {{QUERY_POOL}} thread pool and fetch first page
of the results. In case results set is bigger than one page {{MapQueryLazyWorker}} is started
and link with {{MapNodeResults}} to handle next pages lazy.

This message was sent by Atlassian JIRA

View raw message