Hi Rengan,
There is no definitive calculation for setting the amount of dialog processes when a new dialog instance has been added to a system.
The note <a href="http://service.sap.com/sap/support/notes/39412">39412</a> (How many work processes to configure) is a guideline, you can try the following to increase the amount of work processes gradually:
1) Add one or two additional dialog work processes (e.g. 11 to 13)
2) Do not stop the SAP system for a week - lets say.
3) Using SM50 you can observe if the x additional dialog work processes
were used ( cpu time greater than zero).
It makes no sense to add work processes if nobody uses them.
4) The ideal is a configuration in which at least one (more than one is okay also) work process is always free.
5) if necessary , repeat the above four step with the other kind
of work processes , EXCEPT ENQUEUE work process type)
If this amount of extra work processes allows the instance
to start and there is always one free then this will be enough.
Always ensure that there is at least one more DIA work process compared to the non-DIA work processes. The database instance may also be present on the same host, if this is a central system and for this reason. you have to be careful increasing work process total in case the extra possible load causes performance issues. Note <a href="http://service.sap.com/sap/support/notes/9942">9942</a> (Max. number of work processes) contains more information about possible bottlenecks and limits.
If there is are actual peformance issues overall for system, then it may be best that you create a message in the XX-SER-TCC component later for deeper analysis with an open connection.
I hope some of this information helps.
Regards, Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.