Solution : https://service.sap.com/sap/support/notes/5517 (SAP Service marketplace login required)
Summary :
SAP Note details issues arising in systems (SAP 2.1/2.2 and 3.X) where large dataset operations lead to runtime inefficiencies due to internal table processing and extract handling. The problem arises when a large number of small records sorted by internal tables or extracts cause excessive CPU load due to the limits of the SAP paging buffer, preset to 800 KB. This issue is compounded when the sorted sequence of records greatly deviates from their initial sequence, causing frequent paging block copying, leading to high system and user CPU loads. Recommendations include adjusting the SAP profile parameters for the paging buffer and potentially re-importing sorted datasets to optimize memory management and reduce system strain.
Key words :
==> sap profile parameter rdisp/pg_local, ==> sap profile parameter rdisp/pg_shm, sap profile parameter abap/use_paging, process-specific sap paging buffer, cross-process sap paging buffer, additional key words abap/4, high user cpu load, run-time problem results, high system cpu load, resorted data set prior
Related Notes :
| 311644 | IS-Oil performance: Collective note |
| 73918 | Runtime problems for large internal tables |
| 33190 | Use of resources when sorting in ABAP/4 |