FICO®Xpress Executor is a scalable service for executing optimization models. It allows the user to deploy an Xpress-Mosel model and configure it as an execution service on the Decision Management platform. A REST API allows for multiple concurrent executions of the model. The service includes the ability to connect to thesolution database and interact with other platform services outside the deployed solution. With the release of Xpress Executor 4.0, the service has been re-architected to significantly enhance throughput.
New features in Xpress Executor 4.0:
As part of the architectural changes in Xpress Executor 4.0, the following features have been End-of-Lifed:
For more information and a detailed list of features and fixes, we recommend you read the Xpress release notes.
New features in Xpress Executor 4.0:
- Re-architecture: Xpress Executor has been optimized to support higher throughput per second, improving execution efficiency and overall performance. The compute capacity of each Executor node has increased from 4 to 28 cores.
- Synchronous Execution Endpoint: The execution endpoint has transitioned to a synchronous model. Now, the system returns the results only once the execution is complete, replacing the previous asynchronous API.
- Automatic Run Log Upload: Upon completion of execution, run logs are automatically uploaded to an S3 bucket. These logs are persisted in the solution's designated S3 storage for easy access and auditing.
- Enhanced Configuration Options: Executor can now be configured to allow the model to interact with external components beyond its current solution, increasing flexibility in various use cases.
- Warmup Feature: Executor has a built-in pool of Mosel instances that are reused for executions. Executor can now be configured to warm up each Mosel instance before it is used for regular executions.
As part of the architectural changes in Xpress Executor 4.0, the following features have been End-of-Lifed:
- The mosjvm module for executing Java code has been removed.
- Standalone LP or MPS file solving is no longer supported.
- The SOAP API is deprecated and no longer supported.
- The execution queue view has been removed due to the shift to a synchronous API.
For more information and a detailed list of features and fixes, we recommend you read the Xpress release notes.
Updated 1 year ago
Version 3.0