SAPapplicationperformance

SAPproductionperformanceissue
troubleshooting
PostedonAugust12,2012
Ifyouasanapplicationperformancesupporteriswonderingwhereyoushouldstartto
addressaperformanceissuereportedbyaSAPuser,thenthispostmighthelpyoutoget
started.
SAPperformanceissuetroubleshootingnormallyinvolvesfollowingsteps.

Iwouldliketopointoutthatperformancetroubleshootingcanbeaniteratedprocessinsome
complexsituations.Thereisnoclearcutbetweenthosesteps.Howfastcanyoutrouble
shootaperformanceissue,itdependsonyourexperience/knowledgeonSAParchitecture,
application,database,networkandyourSAPapplicationandsystem.
1.Gatherinformation
Whenaperformanceissueisreportedbyauser,weneedtogatherinformation.Theuseris
expectedtoprovidefollowinginformationasneededbasedontheperformancescenario:
Whatistheperformanceissue/performancedeviation?Whatisexpectedruntimeand
whatistheactualruntime?
Which/whatprogram/job/system/server/userisinvolvedintheissue?
Whendoestheissuestartintermsofsystemtime?
Whatisthesolutionarchitectureoftheprogramanddataflowoftheprogram?
Areotherusersexperiencingthesameissuewiththetransaction/programifmorethan

oneuserarerunningthetransaction?
Howwastheunderlyingtransaction/program/jobexecuted?
Isthereanychangeonthewaywhichtheprogram/jobisexecuted?
Istheprogram/transactionprocessedmorevolumethannormalwhenperformance
issuehappens?
Isthereanyprogramcodechangesontheprogramandwhen?
Isthereanyfunctionalconfigurationchangesrelatedtheprogramandwhen?
Isthis1sttimeanuserencounterssuchperformanceissue?
Isthisonetimeissueorconsistentissue?Whatisthepatternoftheperformanceissue
observed?
Whatiscriticallevelofthisissuefrombusinessoperationpointview?This
understandingwouldnotimpactmethodoftroubleshooting.
Basedonaboveinformation,youthencandigintosystemtogetmoreinformation.For
ongoingissue,youcanstartwithSM50/SM66toverifycurrentstatusofarunning
transactionbasedonworkprocessesstatusshowedinSM50/SM66,youcandecide
whetherthereisanneedtochecksystemhealth(resource,databaseandapplicationlocks
etc)etcyoucanuseST12tocatchoneormoreperformancetracesdependsonthe
scenario.Forperformanceissuehappenedinthepast,youcanstartwith
STAD/ST03N/SM37or/sdf/montogetstatisticsdata.Ifitisajob,youcanuseSAP
transactionSM37tocheckhistoricalruntimeinformation.Ifsm50/sm66showsalldialog
processesarebusy,thenyoucanconcludethisisasystemlevelperformanceissueand
issueislikelyrelatedtoresourceIfSm50/sm66showsonlyafewsapworkprocessare
active,thenyoucanconcludethatsystemresourceisunlikelyacontributortotheissueetc.
However,youmightcometoCPUresourceagainsinceSM50/SM66onlyshowsSAP
processesiffurthercheckfindnousefulhintsorindicateCPUisstillaconcern.For
example,IdidseecaseswhereUXlevelnonSAPprocessesareusingtoomuchCPU
powerwhichisotherwiseavailabletoSAPapplicationandcausingperformanceissue.
2.Verifyperformanceissue
Thisistochecksystemdatabothcurrentandhistorytovalidatethedatawecollectsrelated
totheissue.Thisisimportanttocorrectanyassumption,communicationissuerelatedtothe
performanceissue.Atthisstep,younormallyneedtogethistoricalandholisticinformation
relatedtotheincidentfromjoblogandperformancedatabaseofthesystemetc.
Ihadexperienceswhereuserswerereportingruntimeissuebuttheruntimewasactuallyin
historicalruntimerangeetcProductionperformanceincidentisaboutperformance
deviationandrestoringnormalperformanceofaprogram/job.Also,sometimes,performance
issueisduetorecentchangeswhichhavebeendonewithoutusersawareness.
3.Classifyperformanceissueandidentifysolution
Nowwecometothepointtoclassifyaperformanceissueandidentifythesolutiontothe

issue.Classifytheissueandidentifysolutionmightinvolvefollowingstepsandactions:

Resourcehereisreferringtosystemhardwareresources(CPU,Memory,storage)andtheir
configuration/allocationincludingCPU,memory,IOandsapbasisconfiguration/setting.
LocalsystemisreferringtocombinationofOS+DBMS+SAPbasiscomponents.Remote
system/clientisreferringtoSAPclientandanothersystemwhichtheSAPsystemneedsto
communicatewith.Businesssolution/SAPapplicationhereisreferringtocombinationof
SAPandcustomercoderelatedtoabusinesstransaction/function.Networkissueisreferring
toconnectionanddataflowbetweendifferentsystems.Executionissueisreferringtothe
wayabusinessuserexecuteaSAPtransaction/function.
Resourceissue.
Userconsumptionissuemoreresourcesareutilizedbyapplicationandsystem
andsystemtools
Application/solutionitselflikeprogramdesignetc.
IdentifyimprovementopportunityviaSAPperformancetoolslike
ST12/ST05,SE30etc,changesolutiondesign/code.
Resourcesutilizationissue
Loaddistributionissuecancauseresourceissue
Redistributesystemloadviatool/SDF/MONetc.
Resourceconfigurationissue&Resourceshortageormalfunction
CPUshortageissue(OS06,STADand/orSDF/MON)>Bringmore
capacitytoapplicationserver.
Memoryshortageissue(ST02,OS06,ST04etc)>increasephysical
memory.
Spaceissue(SM21,ST04andDB02etc)>adjustfilespaceortablespace
etc.
IOsubsystemissue.
Othersystemconfigurationlikespool,enqueueetc>adjustsystemsetting
inspoolandenqueueetc.
Localsystemissue.
Tableaccessissue.
Statisticsissue>Update/maintainstatistics(systemorsaptable)via
DB13,RSANAORAtooletc.
Index/tabledatafragmentation/orderingissue>rebuildorreorderthe
table/index.
System/databaseparametersissue>tunecorrespondingsystemor
databaseparameters/setting.

Kernelissue/systembug.
WorkwithSAP+DBMSvendor+OSvendortofixsystemissue.
Remotesystem/clientissue.
Contactremotesystem/applicationownertofixtheissue.
Businesssolution/SAPapplicationissue.
StandardSAPcode/designissue.
WorkwithSAPforthesolution.
Localdevelopedcode/designissue.
Identifyimprovementopportunityviaperformancetoolscodeinspector,
st12,se30orST05etc.
ABAPissue>fixcorrespondingexpensiveABAPstatements.
Databaseaccessissue>fixcorrespondingexpensiveSQL
statements.
Design/configurationissue>changeprogramdesign/relatedfunction
configuration.
Datavolumemanagementissue.
Reviewdataretentionperiodandarchivingsolution.
Networkissue.
Fixnetworkissue.
Executionissue.
Enduserexecutionissue.
Educateendbusinessuserorintroducesystem/programlevelcontrol.
Deploy/schedule/processissue(databaselocksetc)
Redeploy/rescheduleapplication/jobstodifferenttimewindoworadjust
sequenceofexecution.
Whichstepsareneededandwhatstepisexecutedfirstdependsontheperformanceissue
scenarioandyourexperience.Iamjustsharingshowatechnicalroadmapofaperformance
issueresolutionfromtechnicalpointviewandnotabusinessprocess.Forexample,ifan
runningprogramisabortedduetomemoryissue,thenyoucandirectlycheckresourceused
bytheprograminST22andsystemmemoryutilizationandconfigurationviaST02,from
here,youcanconfirmwhetherthisisaresourceissueorprogramissuequite
straightforward,Iwouldcoverthisindetailsinmylaterpostinghowtotroubleshotjob
cancellationduetomemoryissue.
Itisimportanttoclassifywhethertheissueisorwillbeonetimeissue/consistentissue.One
timeperformanceissuecanbeduetoonetimesystemstatus,abnormalapplicationvolume,
networkstatus,improperexecutionetc.Foronetimeissue,thereisnoneedtomakeany
system/programleveltuningorchanges,wejustneedtoreruntheaffected
application/transactionagainproperly.Forexample,whenuserisrunningalargeonetime
loadinbusinessbusyhoursthiscancausesystemperformanceissuewithsymptomlike
CPUshortage,processshortageor/andmemoryshortageetc,butthisisnotatruesystem
resourceissueiftheperformanceissuecanbeavoidedviamorestrictcontrolonthe

executionsuchastimewindowand/orparallelismdegrees.
3.Solutionimplementationandverification
Thisistomakecorrespondingchangeonrelevanttechnicalcomponentand/orthewaythe
applicationisexecutedandverifytheperformanceconcernisgonevianeededperformance
toolslikeSTAD,/SDF/MONetcand/oruserconfirmation.
IamplanningtowritemorepostsinthisarealikehowIcanknowperformanceissueisdue
toprogram/design,howIcanidentifyperformancebottleneckofaprogramandhowIcan
knowsystemisnotarootcauseofperformanceissueetc.
ThisentrywaspostedinSAPsupportandtaggedSAPproductionperformanceissue
troubleshootingsapproductionperformanceissueanalysisSAPproduction
performancebyeric.Bookmarkthepermalink[http://www.sapperf.ca/production
performanceissuetroubleshooting/].
2THOUGHTSONSAPPRODUCTIONPERFORMANCEISSUETROUBLESHOOTING

Vadamalai
onSeptember1,2013at4:28amsaid:

Itsreallynicepostingpleasedopostmaymorerealtimeperformanceissues.

Pingback:replicaoakleysunglasses