
Too many threads....can software exploit it.....
I have talked to a lot of enterprises (mostly large banks, etc) and they think this is not as good as it might seem. Most enterprises tend to run their systems with common application patterns on one set of boxes, so application servers on one box, database servers on another, and so on.
There is some benefit in having a number of threads available, but for the common application pattern environments the software isn't that inherently multithreaded to be able to exploit that large a number of threads, and bottlenecks start to occur in caches, etc. So, a reasonable number of threads with a higher throughput of each is more akin to the software of the day...
I can't see myself telling Oracle with 11G or IBM with WAS to "make your software more multithreaded", as the overheads of synchronisation will become an issue.