Skip to Content

Lumira 2.0 run slowly

Dear All.

I'm recently use Lumira 2.0 to develop report.And the report run slowly,even though I just have one datasource,or I just carry a filter,which will spend several times than SAP BusinessObjects Design Studio.And in design studio,I can add "&PROFILING=X"to analysis time spend.But in lumira 2.0,it haven't design studio convenience,which will show like follow picture.

And my version is:2.0 SP2 (Version: 20.2.0).



profiling.png (62.1 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Sep 07, 2017 at 09:20 AM

    Hi Jing - on an ASUG webcast last week, SAP advised sizing the platform properly, and when installing SAP Lumira 2.0 add-on to the BI platform to put it on a separate "node" - please note I am not a professional BI admin, but perhaps discuss these topics with your BI admin. The Lumira add-on will be "memory hungry" as it has an in-memory 'velocity' engine.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 08, 2017 at 09:18 AM

    Hi Jing - I assume you mean to watch the webcast recording? Webcast recording links are here

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 14, 2017 at 12:32 PM

    Hi Jing, all,

    same here. I have the impression, that eventhough my environment was sized according to the guides and the quicksizer, it performs rather average. Not really very slow, but pretty mediocre. Since we are trying to migrate and sell it to the business, performance is a key topic.

    We are using Designer and Discovery reports (Lumira 2.0 patch 3) on top of BI platform 4.2 SP04 Patch 03 in combination with SAP BW queries.

    Compared to the result time of the data base and the SAP BW query, I think that it should be faster. Because my customer thinks so too, I am highly motivated to find approaches.

    Does anyone know how to analyze or trace the performance? I also tried it with the above mentioned "&PROFILING=X" parameter, but it used to give more insights in the previous versions of the tool.

    Any suggestions?

    Thank you + Best,


    Add comment
    10|10000 characters needed characters exceeded

  • Jan 18, 2018 at 08:09 PM

    We have the same issue. Share with us, Marcus, your findings.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Bill,

      well, as always with performance issues, there was no silver bullet solution.

      What helped was a mixture of different actions:

      • Apply some actions derived from the best practices (see below) like background processing, on startup-skripts and "only load datasources when components get visible" scripts
      • Increase the RAM of the BI platform server
      • Have a closer look at the data origin (SAP BW queries) --> We were able to optimize them and thereby also improve the performance a little

      What might help for your case is to have a look at the design studio performance best practice principles:

      Again, we are not there (to be there would mean to provide a very fast report), but what I count as a first step into the right direction is the achieved improvment.

      Good luck + THX,