on 01-17-2011 1:10 AM
HI,
BPC Report performance is not good at the moment.
The data is not much(about 80k) and we are not using any EV functions or multiple EVDREu2019s on the report.
We have account with desc, comment, 12 periods and four out years on the report.
When ever we insert a row in the input schedule and refresh it in report, it is taking long time to display the change.
We have set NoSend to 'Y' in EVDRE but it still did not improve the performance.
Again, Input schedule performance is far better than report even though both are processing the same data.
Not sure why report is taking long timeu2026
Anyway to improve performance would be much appreciated.
Thanks and Regards,
Venkata
One performance issue I have found is if you have your appset set to a YTD basis, but have your measures set to PERIODIC, you may get some performance degradation of this level. - Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We had to spend a considerable time to investigate and identify this performance issue. In the end we found it is MDX(Calc members). There is scope for significant improvement in this area and util then it is better to disable calculated members in netweaver version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you please share your findings? what are the main reasons for a report low performance?
We dont have too may rows.
But we have all the measures (Periodic, MTD, YTD) , calculated members for current year and prior year etc.
Due to few number of rows and various measures involved - we have used EVGTS with some member values hardcoded in the reports
- We have 5-6 EVEXP functions in each worksheet which is created on 'Entity'
Also we have multiple workseets in a report. The query runs for a considerable time (~15 mins).
What is interesting, Just as a comparison, the same report in the erstwhile OSOFT system takes ~3 mins to run.
Please share your analysis/findings.
Thanks
Dimension formulas will always add to your processing time as they are not stored values, they a calculated each time they are accessed/queried.
Displaying the parent members may also be slowing this report though it should not be an issue in the Netweaver version as it was in the Microsoft version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The Key areas which needs to be checked in case of performance issue in any EVDRE template are,
1. Usage of Cell Key Range - Try to avoid it. (Rather use evget function)
2. Formating - Try to make it simple only for your requirement.
3. Options - Use only limited set of Options
4. Expansion - 80k is considerably huge data set for reporting and in this case try to fix the layout i mean to remove dynamic
expansion and have static report where ever possible(Row or Column).
Hope this should help,
Regards,
G.Vijaya Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vijay,
Thanks for your prompt response.
We are not using cell key range.
Formatting is simple, just highlighting the total rows.
We have tested without formatting and it is sitll taking same time.
80k is the total records in the cube.
Report is fetching about 70 records with 12 periods,4 out yrs and few comments.
It is still runnig too slow. Taking about 60 seconds.
Any other settings we can use to improve performace??
Regards,
Venkata
Hi,
Fetching just 70 records should not take this long time.
Can you please do a test by creating a sample report of that kind, i mean a new evdre report. and do reply if you still face performance issue.
If the new report is working fine, then may be your older be correpted.
If the new report too is having bad perfomance, try optimizing the application and test it out.
Regards,
G.Vijaya Kumar
Vijay,
I have created a new report but the performance did not improve.
I have then taken out caluclated member in the P_DataSrc then performance improved significantly(~6secs)
In P_DataSRC, we have a claculated member which adds manual and import entries when
user has manual entries. I have used MDX formula to add with simple if statement. One option we are thinking
is to use hierarchy node to total but this displays for each row even if there is no manual entry. Performace is good doing this way but need to check with our client. Other option is to store the total value usign script logic or BADI.
Regards,
Venkata
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.