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

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

{panel:title=Branch: [pull/12589/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12589/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8761504&buildTypeId=IgniteTests24Java8_RunAll]

> Calcite engine. Reduce contention by QueryBlockingTaskExecutor
> --------------------------------------------------------------
>
>                 Key: IGNITE-27389
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27389
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: calcite, ise
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently QueryBlockingTaskExecutor uses one lock for add task/poll 
> task/finish task operations. If there are too many threads configured in pool 
> it leads to contention on this lock. Let's analyze how we can reduce 
> contention. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to