Settings that affect system resource use

Component class loader

By default, the PBVM uses per-component class loaders to run components. You can configure components to share class loaders to reduce the memory footprint required to run components. Doing so can improve scalability by allowing more component instances to run in the available memory. For details, see the Sybase white paper Reducing Memory Requirements When Using PowerBuilder Components in EAServer.

DataStore resource footprint

DataStore objects used in components can consume system resources such as memory and Windows user and kernel object handles. When many DataStore objects are instantiated, they can exhaust the available resources unless you have tuned the DataStore settings to minimize resource use. For details on tuning DataStore settings, see the Sybase white paper Operating System Constraints Affecting the Scalability of PowerBuilder DataStores in EAServer.

DataWindow memory management

For large retrievals or imports into a DataWindow object, set the datawindow.storagepagesize property to LARGE. Setting this property allows the DataWindow to most efficiently use the available virtual memory. While the setting LARGE is recommended, a setting of MEDIUM is also available. For more information, see the DataWindow Reference manual in the PowerBuilder documentation.

Bind thread

Disable Bind Thread for PowerBuilder components deployed to EAServer unless instructed otherwise by the documentation that accompanies your PowerBuilder version or Sybase technical support.

For more information on threading issues that affect PowerBuilder components, see the Application Techniques manual in the PowerBuilder documentation.

Garbage collection

The PBVM uses a garbage collection model to free memory used by unreferenced and orphaned objects. For more information on how garbage collection happens in PowerBuilder, see the Application Techniques manual in the PowerBuilder documentation.