You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2020/02/17 12:18:00 UTC

[jira] [Commented] (IGNITE-12663) Let's limit all thread pools' sizes to 5 in tests

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

Stanilovsky Evgeny commented on IGNITE-12663:
---------------------------------------------

[~ilyak] we need i.e. some kind of starvations in common tests coverage, does this fix not a simple masquerade of such a problems?

> Let's limit all thread pools' sizes to 5 in tests
> -------------------------------------------------
>
>                 Key: IGNITE-12663
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12663
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The rationale is, it is very painful shoving through thread dumps of test with N CPU threads in every pool.
> Why 5? Rebalance thread pool is 4 by default, and system pool has to be bigger



--
This message was sent by Atlassian Jira
(v8.3.4#803005)