Cognos Analytics

Expand all | Collapse all

Performance Tuning

  • 1.  Performance Tuning

    Posted Mon March 29, 2021 09:00 AM
    Good Morning,

    I hope that your day has gotten off to a good start.  Which Cognos log files should be refreshed and studied for performance tuning and affinity requests?

    Warm Regards,
    Eli


  • 2.  RE: Performance Tuning

    Posted Mon March 29, 2021 07:05 PM
    Your question:
    >Which Cognos log files should be refreshed and studied for performance tuning and affinity requests?

    In the past I did ipfclientconfig.xml performance analysis. This would give good insights into request hitting GW, APP and DB server, execution time in any component and the time for sending it back to the client.

    In C11.1.x some components of logging have changed, so I am not shure if ipflogging is still the best way to do this.

    In general from ipclient you could understand how much time is lost in GW, APP and DB as well as rendering.

    Affinity is about short term request navigating the portal and triggering execution = low affintiy
    And about retrieving a report from one app.-server doing it = high affinity

    Tuninig this I found it very helpful to use jMeter and rampup usage of high and low affinty, filling up RAM and CPU usage.

    So ... looking at just one logfile is not usefull. In the past, looking at ipfclientconfig.xml and setting up different loggings was the best approach.


    ------------------------------
    Ralf Roeber
    https://linkedin.com/in/ralf-roeber-470425a/
    ------------------------------



  • 3.  RE: Performance Tuning

    Posted Thu April 01, 2021 07:00 AM
    Thanks





  • 4.  RE: Performance Tuning

    Posted Tue March 30, 2021 02:01 AM
    Hello,

    System metrics and thresholds are a good start. You can even extract daily metrics with JMX and compare the results to performance metrics gathered from the operating system. 
    You don't need logs, you need metrics around number of requests processed, wait queue lengths, wait times, and compare that with system resources. If you have requests waiting in queue and system resources are not fully utilized then you can tune accordingly. If resources are fully utilized, you have great information to go back to the business and request more.

    Check out the system management methodology: here

    Even setting up thresholds in the admin portal is a good way to start. Get threshold violations logged to your audit store and write reports to deliver this information direct to your inbox.

    ------------------------------
    Luke Peterson
    Business Analytics Advocate
    IBM
    ------------------------------



  • 5.  RE: Performance Tuning

    Posted Thu April 01, 2021 07:00 AM
    Thanks





  • 6.  RE: Performance Tuning

    Posted Tue March 30, 2021 11:15 AM
    Don't forget also about the the performance details that can be displayed when authoring or editing reports because more often than not the queries impact performance more than anything else.

    https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ug_cr_rptstd.doc/c_rptstd_performance_details.html

    ------------------------------
    Robert Hofstetter
    ------------------------------



  • 7.  RE: Performance Tuning

    Posted Wed March 31, 2021 09:37 AM
    Two points:
    1) After CA release, all logs are enabled in configuration/diagnostic logging without the need to edit ipfclientconfig.xml, applicable to all notes.
    2) Advanced logging analysis:  you can contact your Cognos support and asking for ICETEA.  An advanced logging tool just for Cognos. 
    3) The performance details are being improved in the upcoming 11.2 and waiting for the release and enjoy.

    ------------------------------
    Jijiang (George) Xu
    ------------------------------



  • 8.  RE: Performance Tuning

    Posted Thu April 01, 2021 06:56 AM
    Thanks