Solution : https://service.sap.com/sap/support/notes/724140 (SAP Service marketplace login required)
Summary :
This SAP Note details an issue where extended memory (EM) in SAP systems remains tagged as 'busy' in the OS after being released. The solution involves a kernel patch (CST Patch Collection 15 from April 15, 2004) that allows for customizable release of memory back to the OS, based on defined thresholds and times, minimizing system inefficiencies and potential memory bottlenecks. Parameters including es/disclaim_threshold_MB, es/disclaim_coasting_time_alloc, and es/blockdisclaimsize_KB are adjustable to manage memory release according to the operating system's demands and application needs. This patch is pertinent for managing EM effectively within SAP environments.
Key words :
terms madvise madv_dontneed madv_free disclaim reason, simply retrieve blank pages, question remain memory resident, es/table = shm_segs parameter, hp-ux earlier, 64 bit sun / solaris, smaller em blocks, larger em blocks, memory bottlenecks occur, main memory requirements
Related Notes :
| 860319 | CST patch Collection 28 2005 |
| 835474 | More than 32 GB extended memory |
| 823548 | Decreasing HP-UX performance when you save data |
| 735566 | Documentation for parameter es/disclaim_coasting_time_alloc |
| 730345 | CST patch collection 18 2004 |
| 723952 | CST patch collection 15 2004 |