[
https://issues.redhat.com/browse/JGRP-2482?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-2482:
--------------------------------
Hmm, it seems that the internal thread pool is only used if the regular thread pool is
full and the message is tagged as {{INTERNAL}}!
Perhaps we should change this to:
* regular -> regular thread pool
* {{OOB}} -> regular thread pool
* {{INTERNAL}} -> internal thread pool
* {{OOB|INTERNAL}} -> internal thread pool
Investigate perf impact of this change
Check if the largest thread pool is cluster-size + delta
--------------------------------------------------------
Key: JGRP-2482
URL:
https://issues.redhat.com/browse/JGRP-2482
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Major
Fix For: 5.0.0.Final
When running UPerf in a cluster of 4, we see {{thread_pool_size_largest=39}}. Verify that
MaxOneThreadPerSender works as expected: the largest thread pool size should be 4+delta
(timer threads, retransmission): ~6.
It looks as if {{MPerf}} behaves (~6 threads), but {{UPerf}} doesn't: ~26 threads
--
This message was sent by Atlassian Jira
(v7.13.8#713008)