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

ASF GitHub Bot commented on IGNITE-9171:
----------------------------------------

GitHub user tledkov-gridgain opened a pull request:

    https://github.com/apache/ignite/pull/5076

    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/5076.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 #5076
    
----
commit 044e1e51e6609e92ff46b0650ec8d69afb2b424d
Author: tledkov-gridgain <tledkov@...>
Date:   2018-10-23T09:10:02Z

    IGNITE-9171: save the progress

commit 05ee7dba340395208ab040c7e13710433e44fe1e
Author: tledkov-gridgain <tledkov@...>
Date:   2018-10-24T13:22:02Z

    IGNITE-9171: lazy mode performance optimization for one-page results

commit e2ffb4a9cc83242e3e6c4283319582c1933eb6b2
Author: tledkov-gridgain <tledkov@...>
Date:   2018-10-24T14:25:58Z

    Merge branch '_master' into ignite-9171

commit 7ddcacbfcf484ed359fd1f9e2cbcc6aff414249d
Author: tledkov-gridgain <tledkov@...>
Date:   2018-10-25T12:01:25Z

    IGNITE-9171: lazy mode performance optimization

commit 70be3700b47a1e367f365b049e7872f4ab84efa8
Author: tledkov-gridgain <tledkov@...>
Date:   2018-10-25T12:06:49Z

    Merge master into ignite-9171

----


> 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.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)

Reply via email to