Db2

  • 1.  DSM Slow

    Posted Thu June 25, 2020 02:23 PM
    Whilst the DSM graphical functionality showing where Db2 time is being spent is great, the product has a very long lag to fire up, and can be generally very slow. Currently this is inhibiting our roll-out of DSM to all of our Db2 LUW databases and to the Db2z databases.

    Are there any guidelines regarding how to get DSM to operate with less latency ?
    We are hoping this is just a tuning issue.

    But I worry that the problem might be that it was decided to write DSM in Java (again).
    This lesson should have been learned with the earlier Java-based DB2 GUIs like Control Center.

    Whilst supposedly being deprecated, db2top is lightning fast, so we always default to using that tool for incident management, because IBM have not delivered to us a command line alternative which can troubleshoot critical Db2 outages at the speed required by senior managers.

    Where DSM fits in for us, is in conjunction with products like Dynatrace in order to have a comprehensive Db2 performance dashboard.
    Dynatrace gives us the external Db2 response times from the application perspective, and we are looking to DSM to give us the internal breakdown of those response times within the Db2 space.

    DSM and db2top address completely different performance monitoring requirements, but I am not sure that IBM have actually, or ever, understood that.

    ------------------------------
    Terry Mason
    Legal and General
    ------------------------------

    #Db2