SAP BLOG 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
      
      

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

Similarly the following BW PARAMETERS needs to be tuned, in order to get best response from the BW system.

Recommended
abap/buffersize
# Export/import
rsdb/obj/buffersize
rsdb/obj/max_objects
rsdb/obj/large_object_size
# Exp./ Imp. SHM Buffer (e.g. BW Query Cache)
rsdb/esm/buffersize_kb
rsdb/esm/max_objects
rsdb/esm/large_object_size
# generic key table
zcsa/table_buffer_area
zcsa/db_max_buftab
#single record
rtbb/buffer_length
rtbb/max_tables
# GUI element buffer
rsdb/cua/buffersize
# Nametab
rsdb/ntab/ftabsize
rsdb/ntab/irbdsize
rsdb/ntab/entrycount
# accept BOE SSO logons
login/accept_sso2_ticket
rdisp/wp_no_dia
# rdisp/wp_no_btc
# allow more connections
rdisp/tm_max_no
gw/max_sys
gw/max_conn
rdisp/appc_ca_blk_no
rdisp/wp_ca_blk_no

Okumaya devam et...