[
https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579735#comment-16579735
]
ASF GitHub Bot commented on IGNITE-9171:
----------------------------------------
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4538
IGNITE-9171 Use lazy mode with results pre-fetch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9171
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4538.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4538
----
commit 99b5e863039f5db7c8c8cbae94ef571653e4bdbb
Author: tledkov-gridgain <tledkov@...>
Date: 2018-08-14T12:32:01Z
IGNITE-9171: save the progress
----
> Use lazy mode with results pre-fetch
> ------------------------------------
>
> Key: IGNITE-9171
> URL: https://issues.apache.org/jira/browse/IGNITE-9171
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.6
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Labels: sql-stability
>
> 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)
