Minitab Server analysis latency during concurrent request spikes

Concurrent Job Execution Behavior

Minitab Server is designed to handle multiple user sessions, but the underlying analysis engine manages resource allocation differently depending on the job type. While individual procedures may utilize multiple cores to accelerate a single calculation, there is uncertainty regarding how the system handles the queue when multiple separate analysis requests are submitted simultaneously.

Resource Contention in Shared Environments

In high-load scenarios, particularly with batch job submissions via the command-line interface, CPU and memory contention can lead to significant latency. It is unclear if the engine implements a sophisticated load-balancing mechanism or if it processes these distinct sessions serially, effectively blocking subsequent requests until the current job completes.

Assuming a standard Minitab Server deployment, what is the specific scheduling logic used to prioritize concurrent analysis requests? Does the system support true parallel execution of separate sessions, or is the latency a result of serial processing?