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

Ignite TC Bot commented on IGNITE-9171:
---------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3106920]]

{color:#d04437}RDD{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3106907]]
* JavaEmbeddedIgniteRDDSelfTest.testReadDataFromIgnite (last started)

{color:#d04437}Cache 1{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=3106946]]
* IgniteBinaryCacheTestSuite: 
DataStreamProcessorPersistenceBinarySelfTest.testTryFlush - 0,0% fails in last 
434 master runs.

{color:#d04437}Cache (Full API){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3106942]]
* IgniteCacheFullApiSelfTestSuite: 
GridCacheReplicatedAtomicFullApiSelfTest.testTtlNoTxOldEntry - 0,0% fails in 
last 591 master runs.

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3106998&buildTypeId=IgniteTests24Java8_RunAll]

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

Reply via email to