[ https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623590#comment-16623590 ]
Nikolay Izhikov commented on IGNITE-9171: ----------------------------------------- [~tledkov-gridgain] Do we have a chance to resolve this ticket until the code freeze of 2.7? > 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 > 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)