You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2018/10/02 11:22:00 UTC
[jira] [Commented] (IGNITE-9171) Use lazy mode with results
pre-fetch
[ https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635314#comment-16635314 ]
Taras Ledkov commented on IGNITE-9171:
--------------------------------------
[~vozerov], I fixed lazy worker start/stop synchronization & result set close.
Tests are OK. Please take a look.
> 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: Blocker
> Labels: sql-stability
> Fix For: 2.7
>
>
> 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)