Administering Execution Workers and Services
Xpress Insight executes scenarios by sending jobs to an execution service running on an execution worker. An Xpress Insight execution worker is an instance of the Mosel remote launcher - it accepts jobs from the Xpress Insight server, runs any required scenarios and returns results.
The FICO® Xpress Insight Installation Guide documents how to install execution workers. Once installed and correctly licensed, workers can be mapped to execution services and made available to the Xpress Insight system.
A single execution worker, xsrv:localhost/insight, is available with a Community license.
The division of concerns among execution workers, execution services and execution service mappings provides for find-grained control of the compute resources that can be dedicated to or consumed by executing jobs.
For example:
- You might create a FAST_LANE execution service for small, high-throughput jobs, and a SLOW_LANE execution service for jobs that will take a long time. This arrangement would prevent the slow jobs from blocking the fast jobs.
- By creating several execution services, you can divide the compute resources of a large server into equal (or unequal) chunks for use by several apps with different requirements.
Model developers specify execution modes through Mosel source code annotations, and these are mapped to execution services via the Execution Services page of the admin interface.