Single threaded vs. Multi-threaded Call Object Kernels

We just applied tools release 8.98.4.2 to our test environment and discovered the call object kernels are defaulted to run multi-threaded. Since we came from an older tools release we were running E1 using single-threaded call object kernels.

We've noticed in some of our testing that certain applications seem to be running really slow and 'process' for a long period of time. Has anyone else seen this?

Can you tell me if there should be performance improvements when using the Multi-threaded vs the Single threaded? Are they any gotchas that need to be tweaked or changed which maybe we missed causing this slower performance?

Thanks!!!!

Here is a gotcha:

Given the same hardware between the old single-threaded configuration and the new multi-threaded configuration you may find that your CPU utilization has increased. With Single-Threaded call object kernels there was a throttle to the amount of parallel processing that could occur on the box. The users on the kernel all had to execute in single file. When moving to multi-threaded kernels you often need additional CPU capacity. You users will have better throughput with multi-threaded kernels but this will result in more parallel activity and hence more CPU capacity is required to service that parallel activity.

Regarding the slow transactions, what browser/version are you running? What tools release have you upgraded from? IE 6 is no longer supported and needs some reg hacks to make it work passably.

Are any of your "certain applications" custom ones, especially custom business functions? If so, I believe there is a utility that will check to see if your business functions are thread-safe.