Browse Prior Art Database

CPU Cost Estimator

IP.com Disclosure Number: IPCOM000084000D
Original Publication Date: 1975-Sep-01
Included in the Prior Art Database: 2005-Mar-01
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Winters, RM: AUTHOR

Abstract

Modifications are inevitable during the implementation phase of an application or operating system development. Before a modification is made, a systems analyst should study the performance implications. The overall effect on the performance of the system is usually difficult to predict without a detailed analysis.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

CPU Cost Estimator

Modifications are inevitable during the implementation phase of an application or operating system development. Before a modification is made, a systems analyst should study the performance implications. The overall effect on the performance of the system is usually difficult to predict without a detailed analysis.

Except for sophisticated simulation models, there are no automated facilities that can be used to study the results of proposed modifications. A CPU cost estimation option for a performance monitor could be used, to provide a quick estimation of the overall resulting performance of a modified system.

The CPU cost estimator is an option that can be added to an existing comprehensive performance monitor. The monitor must have a set of collection and reporting capabilities that are sufficient, to identify the amount of CPU spent in each logical section of code. In particular, the monitor must have the following basic capabilities: - Load Module Collection and Reporting - key statistics include the load module name, number of executions, average CPU time spent per execution in code unique to the particular load module. - Task Collection and Report - same as for the load module except for tasks. - Control Program Service Collection and Reporting - same as for the load module, except for the addition of control program services (SVC).

There must also be a user dynamic hooking facility that allows the user to dynamically hook application or supervisory code to collect data when a particular event occurs.

The CPU cost estimator allows the user to define an increase or decrease in CPU time...