Progress startup file

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: The default value for -Ma is 5 and its maximum value is , this value represents the maximum number of queued client processes. If the application requires long and heavy queries and there is performance degradation, -Ma may need to be decreased. Where the value "2" in the formula above will be used by proMon and proShut utilities connect to the DB. In this example assume that 40 users are needed and 8 extra connections are given for promon and other background processes like the Watchdog, the Asynchronous Page Writers, etc.

When using multiple brokers, the count of servers -Mn can be split across brokers using -Mpb: proserve sports -S prosv00 -n 60 -Mn 13 -Mi 4 -Mpb 6 proserve sports -m3 -S prosv01 -Mi 4 -Mpb 6 The "-Mpb" setting of 6 for each broker allows each port to spawn a maximum of 6 servers each. Select the resources tab. Select the database that needs to be edited 4.

Select Configuration 5. Select configuration. Select Edit. Edit Max Users and Max Servers to the required number. Select Save. File generated by OpenEdge Architect Do not edit this file. This is a temporary file and will be removed. However, the reference in ubroker. In this case, the AppServer will fail to start until the -pf startup parameter is removed from the srvrStartupParam property in ubroker.

Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information. Any sample code provided on this site is not supported under any Progress support program or service.

The sample code is provided on an "AS IS" basis. Progress Software Corporation makes no explicit or implied claims to the validity of this information. Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis.

Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose.

The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Product: OpenEdge Version: This is expected behavior. Performance tuning is hard work. To do it right you have to measure various performance metrics and understand what they are telling you. None the less some advice can be offered. It may very well be client settings. In particular you are using -H and -S. If this is a character app or there are app servers and everything is on the same physical server get rid of these.

If you need to keep them then you also need to be explicitly setting -Mn, -Ma, -Mi and, possibly, some others. The 1 "silver bullet" available to you is to set -spin Just do it and say "thank you". That works out to 2GB because a 32 bit system is limited to 2GB of shared memory. The next biggest bang for the buck is to fix that. Create storage areas and put all of your tables and indexes into those storage areas based on the average record size and the level of activity for the table index areas should just correspond to data areas.

NO data should be in the schema area. You should also have the bi cluster size set to a non-default value. As already stated - dump the application's data out of the schema area and load into some new areas.

Will make a dramatic reduction in the number of physical reads the database has to perform to collect the data.