Memory Management simplifications in ABAP Kernel 7.4*Memory Management simpiifications in ABAP Kernel 7.4" TABLE OF CONTENTS OVERVIEW af NEW PARAMETER FORMULAS... TROUBLESHOOTING .. 512. GB LIMIT nnnnnsnese CONCLUSION, 4 5‘Memory Management simplifications in ABAP Kernel 7.4” OVERVIEW This paper describes Memory Management parameterization changes in 7.4” kemel. The main goal of these changes was simplification: the administrator will be enabled by setting only one profile parameter PHYS _MEMSIZE to automatically initiate changes of dependent parameters. This is a fast way to scale the ABAP instance memory consumption. Within the context of this development the “old fashioned” Zero Admin MN for Linux and Windows = was extended to all other operating systems and - _ reimplemented via formula based parameters More information about the Zero Administration in previous releases can be found in: http:tthelp.sap.com/saphelp_erp60_sp/helpdata/en/3c/0586306800924Fe 10000000a114084/content.htm http:/whelp sap.com/saphelp_erp60_sp/helpdata/en/84/7ed384d8 111 1d1 88e0000e83539c3/content htm NEW PARAMETER FORMULAS ‘The formulas may depend on kernel release and operating system. You can get a list of parameters with formula based default values e.g. with help of sappfpar executable. Below is an example for kernel 7.41 PL22 on Linux: > sappfpar all | grep "SAP: (" abaniburersize = (coifS(emfnitel_size_6)"1024"0 15/4096) * 4090) ‘banhheep aroe_total = (max(S(PHYS. MEMSIZE)*1024*1024* 0-1, Slabapthoap_area_dia)*2)) ‘baorograms (Siebseburtersizey4) abap/shared objects_size_MB ‘amPiocksie_ KE feimfglobal_arée_ ME eiminiial 6.48 emmax size MB ralsoPG_ SHEE ‘alsp/ma¥_wensocket_connactions repo ca_bik_n0 ‘selvetabvenicycount (iin(20000, Sfer/ntial_size_MB)"0.02)) (coilSfem/intia_size_1%B) * 024 / 100000 4096) * 4006) (arnt S{emvfntial_size_MB) * 0.05, 32000) (ern(512000, S(PHYS_MEMSIZE) 0.7) (Seminal sze_M48) (max{min(1000+40'max(5 foor{(S(PHYS_MEMSIZE)-126)"25/128), 16984), 1024)) ( S(tsptm_max_no)/2) (Sirasprelem per queue)*3) (S(zcsarib_max_buftab)) ‘salniabftabsze (ean( 00000, ($sau/tabventrycourt))) rrdlvntabvisize (Sirscoetab/Rabsize) *0.2) ‘sdb/ntab/sntabsire (S(rsctuetabstabsize) *01) rsdb/obybutersze (imex(4096 S(PHYS_ MEMSIZE)"102¢ *0.01)) rsatvobyinar_oojects (imax{2000 S(rsabvobybutiersiz) /4)) tsts/oce/eacnad? (Susts/ece/eacnesize)*0.1) ‘obibuter_length (S(eosatable_buffer_area) *0.1/ 1024) ‘Mbhimax_ fables (Stzcsa/th_max_bufab) *01) os inx_burtab (imax(20000 s(zesafable buffer area) /(S * 1024) ) Zesatabie blfer_arca (rn( 2333332383, (max(30000000 (S(amAntal_siza_M48) * 1024 1024 *0.1)))) ES/SHI MAX SHARED SEGS —— ~ ((S(orblobal_area_MB) + Sfabap/shared_objacie_sizo_MB) + Sirbtvbufir_longth)/1024 + ‘S(zrsatiable buifer_sreay/i024/1024 )/ S(ES/SHN_ SEG SIZE) +1) Formulas support in the profiles is implemented as of kemel 7.40, described in: http://help.sap.com/saphelp_nw74/helpdata/en/a7/d631e255594de19809708a3a7c3feB/content him?frames et=/onl51/319798c07a428a896a"0bc2a00adc7 frameset.htmMemory Management simplifications in ABAP Kernel 7.4” ‘sappfpar can also be used for checking your profile >sappfoar pt= check_formula “WARNING: formula parameter absp/buffarsize - 350000 found in profile Errors detected. ° Warnings detected. 1 In the example above the parameter abap/buffersize that has been set to a fix value although its default value is a formula, was found. TROUBLESHOOTING In this section we would like to analyze a “real life” example from an administrator's point of view. A system consisting of 2 ABAP instances is installed on a host with 64GB main memory. Every instance is running with PHYS_MEMSIZE=30% setting in profile. Customers experience sporadic memory lack issues ~ Rabaxes - “EmAllc failed” errors in dev trace = Extended Memory Dump in dev trace : ® exanpies or meron ack Radaxos af: TSV_TNEN. PAGE ALLOG, LOAD. NO_ ROLL, SthNe LENGTH! 100 LARGE. TY THEW BLOOKS NO. ROLL MEMORY ‘The administrator is analyzing Extended Memory Dumps in dev traces, they appear as shown below: Extended Memory Dump Act USER suM MOMs ‘SAP_SMDMON(TS2_UST4E MO) o> oe — a ‘0990FUSRABCD(T#61_U226_IM0) | 23.8) » 23.6< —— USER_TEST.12(7461_U4228M0) [ 238] > 236¢ —- FoHAIN OWNER STATE oo spat foo 1 EG_GLOBAL_AREA shared 2597 1 EG_GLOBAL_AREA shared 2638 2538 SAP_SMOMONIT6_U377_MO) eiachied 12530 2539 KBNZDJEQHUR(TS58_UT5419_M0) detached ‘Tho administrator can't identify any particular user which is using too much memory. This means that the server has been overioaded sporadically, ie. at peak times when many users are working simultaneously.Memory Management simplifications in ABAP Kernel 7.4” Proposed solution: set PHYS_MEMSIZE=45% in the profile to allow every instance to use 64GB * 0.45 = 28,8GB main memory. This will automatically increase the value of dependent parameters, 6.9: PRYS_MEMSIZE=30% PHYS_MEMSIZE=45% erat ee IE 73653 (MB) 20480 (MB) ‘abapihoap_area foal 20452265165 (Byte) 30678397747 (Byte) Keep in mind that the instance has to be restarted for activating its new values! PHYS_MEMSIZE can be also set to absolute values instead of percentage: PHYS_MEMSIZE=40000 which would mean Megabytes in the Example above. 512 GB LIMIT FOR ALL OPERATING SYSTEMS PHYS_MEMSIZE is not a “hard limit’ for an ABAP instance. This is a guide value to make the instance aware about the amount of main memory it should use. This limit can be overrunned in heavy load scenarios 6. It is not recommended to run a Kemel 7.4* has been tested up to PHYS_MEMSIZE=512000 set singular ABAP instance with more than 512000 MB. ‘Warnings in dev traces would give you a hint if you are trying to run an instance with more than that memory size, €.9.: jpCheckPerams:invald value for PHYS_MEMSIZE=600000 [apni mpCheckParams: check massage: Parameter valuo aut of range (16. $12000) [éplnitc] Itis recommended to use default memory management models on every OS: es/implementation = std (Unix) eslimplementation = view (Windows) ES/TABLE = UNIX_STD (Unix) ES/TABLE = SHM_SEGS (AIX only) ‘The memory management parameter formulas have been optimized for the memory model cases above. The only platform has been optimized not for default case only is 08/400 which has been tuned for both UNIX_STD and SHM_SEGS memory models, CONCLUSION Formula based parameters introduced in 7.4% and supported for all operating systems offer a new simplified way of administration for ABAP instances in an SAP system, They will be used in ABAP server memory management already. ‘About the author: Gennady Maly is working at SAP development since 2001.www.sap.com {up BA sap aay Dat Peat BO, 3 eter epm Seana SOS aa sar Sear tasrana er mpoteatadanads 2a 0 Ge ‘eraunten ep posuan osenece nn ren (Siesterieeie ge se tasers ogden ‘es Senn Conte anne Soc nsn Sa Seiteatecsione ne Sauses mae comer “These aie chang te ace Thee ait repensery ob Aone tata pS sy ‘era reso pn a Foner mens hoe a oan ope ‘Granja cones a pees oo cs Sy Maung ooh be craved cosa on ata Elis