|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| The primary function of the <var class="product">SirTune</var> product is to provide information
| | #REDIRECT [[SirTune introduction]] |
| to User Language programmers to make it easy for them to
| |
| improve the performance of their programs.
| |
| This is accomplished in two stages:
| |
| <ol>
| |
| <li>Data is collected in a running Online or <var>BATCH204</var> region.
| |
| This data is obtained by "polling."
| |
| That is, at regular intervals <var class="product">SirTune</var> examines the state of the Online.
| |
| or <var>BATCH204</var> region and records data pertinent to this state.
| |
| <p>
| |
| The part of <var class="product">SirTune</var> that collects this data is called the
| |
| <b>data collection</b> portion, which
| |
| is integrated with the <var class="product">[[Sirius Mods]]</var> for <var class="product">SirTune</var> versions after 1.5, or which
| |
| consists of a separately distributed load module named <b>SIRTUNE</b>
| |
| for <var class="product">SirTune</var> 1.5 and earlier versions. </p>
| |
| | |
| <li>After this data is collected, it is summarized and presented
| |
| in a set of reports that indicate to a User Language programmer the
| |
| potential performance problem areas.
| |
| These problem areas can generally be refined to an arbitrary level of
| |
| detail (for example, individual lines of code in a procedure).
| |
| <p>
| |
| The part of <var class="product">SirTune</var> that summarizes and produces reports is called the
| |
| <b>reporting</b> portion, which consists of a User Language program
| |
| named <var>SIRTUNEREPORT</var>, distributed in the SIRIUS file as part of <var class="product">User Language</var>.</p>
| |
| <p>
| |
| Pre-7.2 releases required a separate reporting load module
| |
| distributed under the name <var>SIRTUNER</var>.</p>
| |