Forum Discussion

WillVitale's avatar
WillVitale
Contributor
2 years ago

Report Speed Performance

Hello,

We are in the process of building workflows . During the demo of required workflow forms, there are some check reports built for users to verify their data and add comments. When the user switches between report tabs in the workflow, the refresh takes approximately 20 seconds to a full minute depending on the report.

Our implementation partner suggested reducing the number of columns. We do have several columns of data, however this is needed for a proper review, and would like to review alternatives before reducing the reporting content.

Is there anything else we can do to increase report refresh speed when there's multiple columns?

Thanks,

Will

Cube View
Reports
  • JackLacava's avatar
    JackLacava
    2 years ago

    I'd say, as generic rules of thumb:

    1. make sure you're not asking humans to perform checks that a machine can do. Leverage Confirmation Rules as much as possible, so that manual review is just not necessary and you can take numbers off that report.
    2. Reduce the number of calculated rows or columns and Dynamic accounts being displayed. Both of those force the system to perform calculation work at display time. Instead, consider performing that sort of work in dedicated accounts or UD8s as part of calculation or consolidation, storing results, so that at display time they are simply retrieved from database. If it's a pass/fail situation, store 1s and 0s.
    3. Try to reduce the number of dataunits being loaded. Provide filters instead, so that users can switch between period/scenario/entity and just have Accounts/Flows/UDs on the page.
    4. If you're using custom dashboards, make sure your extender rules are not doing something funky as part of loading operations - making slow db or network calls, etc.

    Hope that helps.

  • JackLacava's avatar
    JackLacava
    Honored Contributor
    2 years ago

    I'd say, as generic rules of thumb:

    1. make sure you're not asking humans to perform checks that a machine can do. Leverage Confirmation Rules as much as possible, so that manual review is just not necessary and you can take numbers off that report.
    2. Reduce the number of calculated rows or columns and Dynamic accounts being displayed. Both of those force the system to perform calculation work at display time. Instead, consider performing that sort of work in dedicated accounts or UD8s as part of calculation or consolidation, storing results, so that at display time they are simply retrieved from database. If it's a pass/fail situation, store 1s and 0s.
    3. Try to reduce the number of dataunits being loaded. Provide filters instead, so that users can switch between period/scenario/entity and just have Accounts/Flows/UDs on the page.
    4. If you're using custom dashboards, make sure your extender rules are not doing something funky as part of loading operations - making slow db or network calls, etc.

    Hope that helps.