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 Sun, 17 Feb 2019 07:47:00 GMT

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

Vladimir Ozerov commented on IGNITE-9171:
-----------------------------------------

New test reun after merge w/ master: https://ci.ignite.apache.org/viewQueued.html?itemId=3106998

Problems to be addressed:
# Remove default value from {{SqlFieldsQuery}}
# Ticket for OOME tests integration on TC
# Ticket for lazy suite on TC

> 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
(v7.6.3#76005)

Mime
View raw message