Defining a Server

   

Server definition is a significant part of APE modeling. This is where you choose pooling and queuing, configure the workers, and define the resource consumption characteristics of the services.

Pooling is an important design strategy because it quickly recycles objects that have already been created. Queuing is also important because with queuing your application handle increased workloads while balancing resource consumption. You can select pooling only, or both queuing and pooling together (for asynchronous models only).

You can configure the worker options using the following four parameters.

The CPU task option simulates real work by specifying task and sleep duration. You can investigate CPU availability by adjusting the CPU task workload on server machines.

Regardless of the work simulation determined by these settings, the only "real" work performed by APE's built-in service components is to return the data requested by the client. For more accurate measurement, you can substitute your own object method as a service. To do this, you specify a string of the form "Library.Class.Method", where Library is typically the name of your object server, Class corresponds to one of its publicly exposed object classes, and Method is any method implemented by the Class that requires no parameters.