One of the os/vs2 Release 2 design objectives is to provide each installation with control over the responsiveness and turnaround times of its batch jobs and TSO commands, without requiring installation personnel to write their own scheduling algorithm. Installation personnel specify their response and turnaround objectives in terms of the rates at which processing resources are to be provided to individual jobs and commands. The system resources manager uses swapping to dynamically adjust the execution mix in order to achieve two distinct, but potentially conflicting, performance objectives. The first objective is service — to distribute processing resources among the batch jobs and TSO commands, according to installation specifications. The second performance objective is throughput - to optimize the use of CPU main storage and I/O resources, given the service objectives.
No takes yet. Share an insight, caveat, or question.
Lynch et al. (1974) studied this question.
Synapse has enriched 5 related papers. Consider them for comparative context: