Administering Execution Workers
When deployed on the cloud, the Xpress Insight server provides a local execution service with one local execution worker that is suitable for small/medium jobs.
High capacity worker servers can be added as part of a paid contract and deployed for use with Xpress Insight.
The division of concerns among execution services and execution service mappings provides for fine-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 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.
© 2001-2019 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.