Initializing help system before first use

Developer Responsibilities

Xpress Insight does not support thread-based scheduling for Python-based apps. Best practice recommends that Python apps should enforce a fixed limit on the number of threads used by the job. One way to achieve this is by setting the threads control on the Solver instead of leaving it running with the default (which is to consume all available threads on the host machine). A predictable thread requirement for a job allows the system administrator to use the job count limit to configure the appropriate number of concurrent jobs for a given worker.

Covered Topics
  • Scenario Execution and Job Scheduling
    When scenario execution is initiated, via the app's user interface or the REST API, the scenario is locked to prevent further changes to its data and a job is created. The job descriptor will include the specific execution mode that was requested when the execution was initiated. The job is added to job queue and will be visible on the JOBS page of the user interface.
Parent Topic Execution Modes

© 2001-2022 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.