Solution : https://service.sap.com/sap/support/notes/9942 (SAP Service marketplace login required)
Summary :
The maximum number of work processes for an instance in SAP varies by release and is influenced by factors such as available resources, OS limits, and display capabilities. Releases 4.6D and beyond support more than 100 processes; however, practical constraints often limit this to 100. Essential prerequisites include sufficient event flags, correctly configured SAP parameters (e.g., rdisp/tm_max_no), and a higher OS process count. While a single large instance may improve memory efficiency and load balancing, it raises risks of bottlenecks and complex monitoring. Conversely, multiple smaller instances mitigate resource contention but may increase overall process counts.
Key words :
active work processes increases slowly compared, parameter rdisp/tm_max_no specifies, long-running processing steps, long-running database queries, rdisp/tm_max_no > work processes + number, variable event keys exhausted, sessions lower total number, sap-internal event flag, lower main memory requirements, higher process change rate
Related Notes :
1499097 | Core file in work directory, more then 255 wp's configured |
972262 | Inst.NW 7.0(2004s)SR2/Business Suite 2005 SR2-UNIX |
969660 | 6.20/6.40 Patch Collection Installation : Unix |
967124 | 6.20/6.40 Patch Collection Installation: Windows |
966416 | Inst. SAP NetWeaver based on Kernel 7.10 - UNIX |
965569 | SAP NetWeaver Based On Kernel 7.10: Windows |
927734 | SAP NetWeaver 2004s SR1 Installation: IBM eServer iSeries |
921593 | (Outdated) Inst. SAP NetWeaver 7.0 (2004s) SR1 - UNIX |
919105 | SAP NetWeaver 7.0 (2004s) SR1 Installation on Windows |
785925 | SAP Web AS 6.40 SR1 ABAP Installation on UNIX |
785850 | SAP Web AS 6.40 SR1 Java Installation on UNIX |
735057 | CST Patch Collection 20 2004 |
492208 | INST: SAP Web AS 6.20 Installation on UNIX |
179224 | Doc.no.assignment for unbuffered number ranges |
39412 | How many work processes should be configured? |