Topic
  • 3 replies
  • Latest Post - ‏2013-10-31T17:24:48Z by dattark
9V4Y_George_Chen
9V4Y_George_Chen
2 Posts

Pinned topic how to speed up DB2 connection time

‏2013-10-25T01:41:46Z |

Hi everyone,

 

Has anybody noticed that DB2's connection time is much more than Sybase on Linux server?

In my test environment, DB2's single connection time  arround 70ms to 220ms, while Sybase less than 10ms.

How to improve the DB2 connection speed on Linux server?

Thanks a lot!

 

George

Oct 25

  • dattark
    dattark
    17 Posts

    Re: how to speed up DB2 connection time

    ‏2013-10-25T19:44:19Z  

    Adjust the "num_initagents" in the database configuration. Default is zero.

    Also see value for "num_poolagents" to keep in pool.

    Details covered in DB2 info center.

     

  • 9V4Y_George_Chen
    9V4Y_George_Chen
    2 Posts

    Re: how to speed up DB2 connection time

    ‏2013-10-31T07:37:47Z  
    • dattark
    • ‏2013-10-25T19:44:19Z

    Adjust the "num_initagents" in the database configuration. Default is zero.

    Also see value for "num_poolagents" to keep in pool.

    Details covered in DB2 info center.

     

    Thanks dattark!

    I adjusted the "num_initagents" and "num_poolagents" in the database configuration.

    But there's little change happend. On the other hand, there's dramatic change when I activate the testing database.

    In my current test environment, the average connection time without activating database is around 570ms, after activating the testing database, the connection time is around 25ms.

    I have also done the same test using MySQL, the average connection time is around 1.4ms, much much faster than DB2.

    Activating database could improve connection speed for DB2, but I'm not satified yet comparing with MySQL.

    All the database connections above are using unixODBC on CentOS.

     

  • dattark
    dattark
    17 Posts

    Re: how to speed up DB2 connection time

    ‏2013-10-31T17:24:48Z  

    Thanks dattark!

    I adjusted the "num_initagents" and "num_poolagents" in the database configuration.

    But there's little change happend. On the other hand, there's dramatic change when I activate the testing database.

    In my current test environment, the average connection time without activating database is around 570ms, after activating the testing database, the connection time is around 25ms.

    I have also done the same test using MySQL, the average connection time is around 1.4ms, much much faster than DB2.

    Activating database could improve connection speed for DB2, but I'm not satified yet comparing with MySQL.

    All the database connections above are using unixODBC on CentOS.

     

    In our online transactional environments (version 9.5) we have not noticed connection timing issues so have never really measured them.