We tested this and we found out (on Linux) that you must not configure
MAXCPU higher than the number of _physical_ CPUs. Our box was significantly
slower when we put MAXCPU to the virtual CPU number.
After some testing with MAXCPU and HT, we came to the conclusion that setting MAXCPU to the physical # of CPUs, as Markus wrote, and leaving HT activated (if there are some non-maxdb-processes to be run) seems to be the most performant option.
We've tested this on a 2-way 32bit-Xeon, running 7.5.00.23.
Performance differs about felt 10 to 15 percent. (I wasn't quite in the mood for setting up a complete performance-testing-framework ;-))
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
