Runtime environments for SPSS Modeler

When you run an SPSS Modeler flow in a project, you choose an environment template for the runtime environment. The environment template specifies the type, size, and power of the hardware configuration, plus the software template.

Default runtime environments

You can use this type of runtime environment with SPSS Modeler:

Default SPSS Modeler

The Default SPSS Modeler environment template has the following hardware configuration:

CPU: 2 CPU
Memory: 8 GB RAM
Storage: Uses the worker node storage. The amount of space depends on what is available on the node.

Building a custom runtime image

You can create a custom runtime image for SPSS Modeler if you want tailor a runtime environment to your specific requirements.

For more information about the process, see Creating a custom runtime environment

The following sections are just a few examples of what you can configure in your custom runtime image.

Configuring idle timeout for SPSS Modeler runtimes

Timeout values for a runtime environment determine how long a runtime or session can sit idle before it is stopped or deleted. You can adjust the following timeout values to better suit your workflow requirements:

IDLE_SESSION_TIMEOUT_MINUTES: This value sets how long a runtime can be idle before it is stopped. It triggers when the user interface is still connected to the runtime pod but there is no activity.: By default, idle SPSS Modeler runtimes are automatically stopped after 15 minutes of inactivity to conserve compute resources.
SESSION_TIMEOUT_MINUTES: This value set how long an idle session remains before being deleted. After the timeout, the session is deleted and the pod/runtime is deleted if there are no more active sessions.: The default is 100 minutes.

If you increase the time for both of these values, the changes might result in more resources being consumed within the cluster.

The new timeout value applies to all new SPSS Modeler runtime sessions. Active runtimes continue to use their original timeout setting until they are restarted.

Disabling SQL pushback for the Flight service

In some scenarios, you might want to enable the Flight service to use a connection but disable the SQL optimization (SQL pushback) that runs through the Flight service. For example, you want to use SQL pushback, but it causes compatibility issues with specific data sources that are connected through the Flight service. In these cases, you can use the DISABLE_FLIGHT_SQLPUSHBACK environment variable.

When this variable is set to true, connections through the Flight service continue. However, SQL pushback operations through the Flight service are disabled. Instead, when the SQL optimization is enabled, data sources that can use ODBC drivers for SQL pushback operations revert back to using those drivers.