[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-9441:
------------------------------
Labels: GeodeOperationAPI pull-request-available (was:
pull-request-available)
> The NestedFunctionExecutionDistributedTest uses too many threads
> ----------------------------------------------------------------
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Barrett Oglesby
> Assignee: Dale Emery
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
