[jira] [Updated] (TAP5-1563) ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE
[ https://issues.apache.org/jira/browse/TAP5-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Blower updated TAP5-1563: -- Description: ParallelExecutor service is bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. This is unexpected behaviour for someone not familiar with the ThreadPoolExecutor design, which is not intuitive. The documentation of ParallelExecutor is very misleading and should be expanded to explain this correctly. This blog post I found explains it clearly: http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size was: ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. This is unexpected behaviour to someone not familiar with the ThreadPoolExecutor design, which is not intuitive. The documentation should be expanded to explain this correctly. This blog post I found explains it clearly http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE -- Key: TAP5-1563 URL: https://issues.apache.org/jira/browse/TAP5-1563 Project: Tapestry 5 Issue Type: Improvement Components: documentation, tapestry-ioc Reporter: Andy Blower Priority: Minor ParallelExecutor service is bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. This is unexpected behaviour for someone not familiar with the ThreadPoolExecutor design, which is not intuitive. The documentation of ParallelExecutor is very misleading and should be expanded to explain this correctly. This blog post I found explains it clearly: http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1563) ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE
[ https://issues.apache.org/jira/browse/TAP5-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Blower updated TAP5-1563: -- Component/s: documentation Priority: Minor (was: Major) Description: ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. This is unexpected behaviour to someone not familiar with the ThreadPoolExecutor design, which is not intuitive. The documentation should be expanded to explain this correctly. This blog post I found explains it clearly http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size was:ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. Issue Type: Improvement (was: Bug) Affects Version/s: (was: 5.2.4) ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE -- Key: TAP5-1563 URL: https://issues.apache.org/jira/browse/TAP5-1563 Project: Tapestry 5 Issue Type: Improvement Components: documentation, tapestry-ioc Reporter: Andy Blower Priority: Minor ParallelExecutor service appears to be bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed at once rather than the maximum of 20. This is unexpected behaviour to someone not familiar with the ThreadPoolExecutor design, which is not intuitive. The documentation should be expanded to explain this correctly. This blog post I found explains it clearly http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
