Svennig said:An interesting point - go to Activity monitor. Sort by threads.
DVD Player 8 threads
Safari 7 threads
ITunes 7 threads
iCal 7 threads
...
In total, I have 209 threads in 61 processes, about 4 threads per process. If those threads suffer the same issues as MySQL does, then the performance of all those programs is being greatly reduced.
This affects users, whether they notice it or not. They'll almost certainly notice it if apple don't fix it and they install Leopard +1, or +2 (where the performance problem could be made more evident by the ageing hardware). It reduces the lifetime of your Mac!
Also, remember that now we have the intel transition people can do a direct apples-to-apples comparison. We're in a position where we can compare the "MUCH slower and bloated" Dell running Windows to a Mac. If OS X doesn't stand up, Microsoft can say "Macs might be pretty, but they are more expensive and don't perform as well as <X BRAND> cheaper PC running our Windows operating system".
It is not the number of threads that are alive at the same time that is the problem, it is thread creation and destruction. An application that creates thousand threads and then uses them while it is running has no problems. An application that tries to create and destroy thousand threads every second has a problem, and that is something that applications don't usually have any reason to do.
And applications that _do_ have a reason to work that way just create some threads initially, give them work to do, and when the work is finished, the thread is stopped and restarted when there is more work to do. This avoids the problem quite easily.