Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only
  • 1.  Performance improvement of Stacked Bar Chart

    Posted 30 days ago

    Hi,

    I am trying to improve the performance of a stacked bar chart in a Cognos dashboard. Please see the image. There are other charts in the dashboard which run faster but this chart runs forever causing the dashboard not to load when I run it for an year other than the current year which is the default. The chart pulls data of 4 arrear buckets (30, 60, 90, and 120) as stacks for each month for the last 5 years. On exploring I found that it is the rendering of the chart and not the query itself that is causing the issue. Please suggest solutions/alternatives.

    The viz displays amounts of arrear buckets (30, 60, 90, 120) for each month of the last 5 years (60 months)



    ------------------------------
    Mack L
    ------------------------------


  • 2.  RE: Performance improvement of Stacked Bar Chart
    Best Answer

    Posted 30 days ago

    Hi Mack,

    my first suggestion is to check the "Show Values" properties. I once had the exact same issue that the rendering of a chart took way to long to finish. It was the collission mode combined with the value location and "Show leader lines". My first try was to set the collission mode to "Coarse Stagger" which improved the rendering a lot. Have you tried that?

    I run a quick trial with GO Sales and can reproduce the issue with "Fine Stagger"  immediately. 

    Coarse renders in 931ms and "Fines" takes 3874ms -> 4x times more.



    ------------------------------
    Robert Dostal
    Principal Expert BI
    GEMÜ Gebr. Müller Apparatebau GmbH & Co. KG
    Kupferzell
    ------------------------------



  • 3.  RE: Performance improvement of Stacked Bar Chart

    Posted 24 days ago

    @Robert Dostal

    It worked!. Thank you. The dashboard now takes 3 to 4 minutes to run compared with earlier when it was taking forever. I need to check if I can use the setting to other charts causing the performance issue in the dashboard.



    ------------------------------
    Mack L
    ------------------------------



  • 4.  RE: Performance improvement of Stacked Bar Chart

    Posted 23 days ago

    Cool @Robert Dostal. good info :-)



    ------------------------------
    Jens Bäumler
    Cognos Analytics, Planning Analytics and watsonx
    Apparo Group
    Germay
    www.apparo.de
    ------------------------------



  • 5.  RE: Performance improvement of Stacked Bar Chart

    Posted 23 days ago

    @Jens Bäumler Cognos needs a substantial amount of ressources if the collision mode is set to "Fine stagger" when the displayed data overlaps a lot and there are a little bit to many of them to be displayed. I tried with GO sample data and years nested with months w/o any filter. The amount of values to be displayed overloads the collision check for the chart and the report runs forever with Cognos calculating the best way to display values w/o collisions.



    ------------------------------
    Robert Dostal
    Principal Expert BI
    GEMÜ Gebr. Müller Apparatebau GmbH & Co. KG
    Kupferzell
    ------------------------------



  • 6.  RE: Performance improvement of Stacked Bar Chart

    Posted 23 days ago

    Can anything be done to further to improve the performance of the report. Currently it is taking 1 to 2 minutes depending on the data volume (I have applied coarse stagger to all the stacked column charts in the report)?. I am interested in report level actions.



    ------------------------------
    Mack L
    ------------------------------



  • 7.  RE: Performance improvement of Stacked Bar Chart

    Posted 23 days ago

    Hi Mack,

    to check if it's still related to the collision mode: deactivate it completely and check the run time of the report again. I've seen great improvements when the mode was set to 'none'. If that is the case, then it is the collision mode (still). (Run report with "include performance details".
    Otherwise it's hard to tell what ca be done on report level w/o knowing more details. Maybe it's worth a try to set the execution mode of the queries to 'Concurrent'  and enable caching.



    ------------------------------
    Robert Dostal
    Principal Expert BI
    GEMÜ Gebr. Müller Apparatebau GmbH & Co. KG
    Kupferzell
    ------------------------------