[
https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037080#comment-17037080
]
Andrey N. Gura commented on IGNITE-12663:
-----------------------------------------
[~ilyak] 3 is pretty good number. But we don;t talk about numbers )
There are many tools that simplify thread dump analysis. E.g. Idea collapse
similar threads into groups. If scrolling is problem for you just use quick
navigation with patterns. I believe grep, sed and thread dump analysis tools
will help you. There is no need to change code for it.
> Let's limit all thread pools' sizes to 3 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 3? It should allow all kinds of race conditions to still happen. Of
> course, we should allow specific tests to override this value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
