transactions/big lists.
System performance cannot improve if Dia and Bck workprocess increased. In fact those itself will bring down the performance of the system.
* Do not allocate more the 2 bck process in peak hours
* Check if your hardWARE is adequately sized for these many users.
* Check for any jobs consuming more than 60% of you resource.
( STO6-DETAIL ANALYSIS-TOP CPU)
* Check if there is any NETWORK COLLISION AT SERVER AND USER END.
* Rate of ARCHIEVE LOG SWITCH OVER .
* All USERS use SAME SERVER AT A TIME
* Even USER with ALL SUPER USER AUTHORISATIION can bring DOWN SYSTEM PERFORMANCE AT TIMES
* TRANSPORTS, providing AUTHORISATION and EXECUTING RESOURCE CONSUMING REPORTS TO BE AVOIDED at PRIME TIME.
ABAP,ABAP report,Interactive Report,ALV grid,ALV list,IDOC,User Exit,RFC,Smartform,sapscript,ABAP Performance,Remote Function Module( RFC ),Function Module,Modularization techniques,ABAP tools,ALV report Generator,ABAP Interview Questions,BDC,BAPI,ALE,BADI, EDI,InternalTable,DataStructure,LSMW,Domain,DataElement,Basis and Administration ,ABAP HR development,ABAP Debugger,BW,ExceptionHandling,Download FI, CO, MM, PP, SD, PM, PS, QM, SM, HR, BW, APO,ABAP Tutorial
Tuesday, December 9, 2008
Reason for the SAP R/3 System Running Slow
Check if there are long running jobs in the background during the peak times (SM50) or if users are running long running
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment