[GLASSFISH-19183] [Perf] Number Grizzly Selector threads should match the number of worker threads, if they are less than number of processors on the machine Created: 18/Oct/12  Updated: 03/Dec/12  Resolved: 19/Oct/12

Status: Closed
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: deep_singh Assignee: Ryan Lubke
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any OS; Machine with large number of processors


Tags: PSRBUG

 Description   

While running some performance tests and profiles on a Niagara T2000 machine, it was observed that Grizzly would create a very large number of NIO Selector threads, much more than number of worker threads. The default selector threads count depends on number of processors running on that machine.

Issue GLASSFISH-19182 would help configuring the count of selector threads. But also we can keep the number close to number of worker threads, if that is much lesser than number of processors on the machine.


Generated at Sat Aug 27 17:24:33 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.