anyone familiar with this issue?



We seem to have run into a performance snag with DB2.


We were running DB2 on a box with 8 CPUs and ample memory. What we noticed is that the number of Glassfish Application processing threads seems to decrease exponentially in processing throughput from 8 to 16 to 32 and so on.


We noticed that with 8 threads, DB response was at 2 milliseconds, at 16 threads 1 second, at 32 threads 2 plus seconds and so on...


SO the question is...


Is there a DB2 tuning parameter that allows multiple parallel threads to run concurrently without decreasing processing throughput? Or must we always parallel the threads to the number of processors on the DB Server to retain optimal query/DB response times?

I guess you are having contention issues. Have you checked your CPU utilization when you are seeing slowdown ?