To reduce processing overhead and improve Web request performance, OpenEdge Management and OpenEdge Explorer provide built-in process pooling. Process pooling maintains several instances of _progress running persistently. As an alternative to using built-in process pooling, you can configure process pooling to use an AppServer.
You can disable process pooling to stop instances running in the background. If you disable process pooling, however, you might notice a short delay as you navigate through certain Web pages, such as the Tenant details page for a database enabled for multi-tenancy.
Built-in process pooling is configured with global settings that apply to all local and remote AdminServers that are running under the OpenEdge Management or OpenEdge Explorer instance. You can also configure process pooling for each AdminServer that allows you the flexibility to vary settings individually for remotely residing databases.
