Technical Articles
Performance tuning of LUMIRA reports running on BW – Part 1
Introduction
While trying to view Lumira reports, running on top of “BW as a data source”. It’s observed that multiple parallel connection are established between Lumira and BW servers.
i.e. if a report has 10 charts, then 10 independent connections gets established to BW server, inorder to get the details of each cart independently. In the process making the report open faster.
Thus it becomes necessary to understand, how to MONITOR & TUNE the BW server, in order to handle these parallel request in a much efficient way and in the process achieve better PERFORMANCE.
Monitoring BW system
1. Transaction – SMGW ( Gateway Monitor )
Gateway Monitor is used for administrating and analysing the gateway connections established between Lumira and BW systems. This transaction could be used in monitoring, how many gateway connections are established while viewing one Lumira report.
- Login to SAP Logon -> Execute SMGW transition (before viewing the Lumira report) and note down the number of connections
- Open the Lumira document via Launchpad
- Now refresh the SMGW transaction page and note down the number of connections
- The difference is calculated. In this case 8 connections have been established while viewing a single lumira document.
- Thus to calculate the number of connection required to run 40 reports in parallel is 320 => 320 connections = 40(reports) * 8(connection/report)
- Which needs to be updated in the BW profile parameters
- By executing RZ10 transaction and updating the values for the below BW parameter accordingly
- GW/MAX_SYS -> MAXIMUM NUMBER OF GATEWAY CLIENTS
- GW/MAX_CONN -> MAXIMUM NUMBER OF ACTIVE CONNECTIONS
- By executing RZ10 transaction and updating the values for the below BW parameter accordingly
Note: If the number of connection reaches the maximum limit, then it is recommended to increase these BW profile parameters
2. Transaction – SM50 ( Process Overview )
Process Overview is used to monitor and manage work processes. This gives us information w.r.t. the number of “Dialog/Update/Background/Spool/Update” work process being used at runtime.
- Login to SAP Logon -> Execute SM50 transition (before viewing the Lumira report) and note down the number of Dialogue Work process
- Open the Lumira document via Launchpad
- Now refresh the SM50 transaction page and note down the number of connections
- The difference is calculated. In this case “1 Dialogue Work process” is established while viewing a single lumira document.
- Thus calculating number of “Dialogue Work process” needed to run 40reports in parallel is 40 => 40 Dialogue Work process = 40(reports) * 1(Dialogue Work process/report)
- Which needs to be updated in the BW profile parameters
- By executing RZ10 transaction and updating the values for the below BW parameter accordingly
- RDISP/WP_NO_DIA -> NUMBER OF DIALOGUE WORK PROCESS
- By executing RZ10 transaction and updating the values for the below BW parameter accordingly
Following are the recommended BW parameter values, for 40 concurrent users viewing “Lumira Medium Sizing document.
BW PARAMETER VALUES |
abap/buffersize = 1,00,00,000 |
# Export/import |
rsdb/obj/buffersize = 2,00,000 |
rsdb/obj/max_objects = 80,000 |
rsdb/obj/large_object_size = 15,00,000 |
# Exp./ Imp. SHM Buffer (e.g. BW Query Cache) |
rsdb/esm/buffersize_kb = 2,00,000 |
rsdb/esm/max_objects = 3,000 |
rsdb/esm/large_object_size = 7,00,00,000 |
# generic key table |
zcsa/table_buffer_area = 90,00,00,768 |
zcsa/db_max_buftab = 6,00,000 |
#single record |
rtbb/buffer_length = 2,50,000 |
rtbb/max_tables = 5,000 |
# GUI element buffer |
rsdb/cua/buffersize = 70,000 |
# Nametab |
rsdb/ntab/ftabsize = 9,00,000 |
rsdb/ntab/irbdsize = 60,000 |
rsdb/ntab/entrycount = 15,00,000 |
# accept BOE SSO logons |
login/accept_sso2_ticket = 1 |
rdisp/wp_no_dia = 50 |
# rdisp/wp_no_btc = 40 |
# allow more connections |
rdisp/tm_max_no = 2,000 |
gw/max_sys = 2,000 |
gw/max_conn = 2,000 |
rdisp/appc_ca_blk_no = 2,200 |
rdisp/wp_ca_blk_no = 6,000 |
Note: The above recommended BW PARAMETER VALUES are subjected to change, based on the kind of load applied on the BW system.
Please also go through the below link, having further steps to monitor performance of BW systems
https://blogs.sap.com/2018/11/02/performance-tuning-of-lumira-reports-running-on-bw-part-2/
Thanks for sharing, I will make use of SMGW.
In your example, were you using processing groups in Lumira Designer?
I find AL08 also good for monitoring the number of RFC’s.
Hello Stephen,
True, the processing groups used in this example was for "Lumira Designer".
AL08 transaction also compliments, in monitoring RFC's.
Regards,
Mandanna