SirTune reports - Revision history

DCameron: /* Use REPORT or to specify which reports to produce */

2017-08-15T09:01:13Z

Use REPORT or to specify which reports to produce

← Older revision		Revision as of 09:01, 15 August 2017
Line 39:		Line 39:
	In XML format, these default reports are specified like this:		In XML format, these default reports are specified like this:
	<p class="code"><SirtuneInput maxDelay="10" top="50">		<p class="code"><SirtuneInput maxDelay="10" top="50">
	<report type="info">		<report type="info"/>
	<report type="state">		<report type="state"/>
	<report type="waittype">		<report type="waittype"/>
	<report type="what" state="rung">		<report type="what" state="rung"/>
	<report type="eval" state="rung">		<report type="eval" state="rung"/>
	<report type="eval" state="rung" chunk="4000">		<report type="eval" state="rung" chunk="4000"/>
	<report type="eval" state="rung" chunk="400">		<report type="eval" state="rung" chunk="400"/>
	<report type="eval" state="rung" chunk="4">		<report type="eval" state="rung" chunk="4"/>
	</SirtuneInput>		</SirtuneInput>
	</p>		</p>

JAL: link repair

2017-08-08T21:00:48Z

link repair

← Older revision		Revision as of 21:00, 8 August 2017
Line 245:		Line 245:
	</table>		</table>

	To produce the DISKIO reports, you must specify this [[SirTune ~~configuration~~ statements#colstat\|COLLECT statement]] in the <var class="product">SirTune</var> data collection input stream (<code>SIRTUNEI</code>):		To produce the DISKIO reports, you must specify this [[SirTune data collection statements#colstat\|COLLECT statement]] in the <var class="product">SirTune</var> data collection input stream (<code>SIRTUNEI</code>):
	<p class="code">COLLECT DISKIO</p>		<p class="code">COLLECT DISKIO</p>
	<ul>		<ul>
Line 450:		Line 450:
	</ul>		</ul>
	<p>		<p>
	This is important because, unless the [[SirTune ~~configuration~~ statements#allcomp\|ALLCOMP]] option was specified for the data collection portion of <var class="product">SirTune</var>, non-precompiled or non-APSY procedures will not show up on chunk reports.</p></td></tr>		This is important because, unless the [[SirTune data collection statements#allcomp\|ALLCOMP]] option was specified for the data collection portion of <var class="product">SirTune</var>, non-precompiled or non-APSY procedures will not show up on chunk reports.</p></td></tr>

	<tr><th>EVALI</th>		<tr><th>EVALI</th>
Line 520:		Line 520:
	in the report. Note that to produce this report, data must be collected		in the report. Note that to produce this report, data must be collected
	for state <code>SWPG</code> by <var class="product">SirTune</var>.		for state <code>SWPG</code> by <var class="product">SirTune</var>.
	This would require a [[SirTune ~~configuration~~ statements#colstat\|COLLECT statement]] in SIRTUNEI for <var class="product">SirTune</var>.		This would require a [[SirTune data collection statements#colstat\|COLLECT statement]] in SIRTUNEI for <var class="product">SirTune</var>.

	To get a breakdown of users waiting for journal I/O by evaluating procedure,		To get a breakdown of users waiting for journal I/O by evaluating procedure,
Line 558:		Line 558:
	<li>There are never any users waiting for server.</li>		<li>There are never any users waiting for server.</li>

	<li>No [[SirTune ~~configuration~~ statements#colstat\|COLLECT statements]] were coded to tell <var class="product">SirTune</var> to collect data for		<li>No [[SirTune data collection statements#colstat\|COLLECT statements]] were coded to tell <var class="product">SirTune</var> to collect data for
	users in state WTSV.</li>		users in state WTSV.</li>
	</ul>		</ul>

JAL: link repair

2017-08-08T19:53:32Z

link repair

JAL: mention M204PROC

2017-06-09T00:00:14Z

mention M204PROC

Show changes

ELowell: /* Use REPORT or to specify which reports to produce */

2017-06-08T21:12:44Z

Use REPORT or to specify which reports to produce

← Older revision		Revision as of 21:12, 8 June 2017
Line 58:		Line 58:
	</blockquote>		</blockquote>

	In addition to these, a variety of other reports can be produced upon request. These reports ~~can~~ are requested via the REPORT statement (see		In addition to these, a variety of other reports can be produced upon request. These reports are requested via the REPORT statement (see
	example in [[SirTune report generation#repsmvs\|Generating reports prior to Sirius Mods 7.2: MVS]]		example in [[SirTune report generation#repsmvs\|Generating reports prior to Sirius Mods 7.2: MVS]]
	or [[SirTune report generation#repscms\|Generating reports prior to Sirius Mods 7.2: CMS]]).		or [[SirTune report generation#repscms\|Generating reports prior to Sirius Mods 7.2: CMS]]).

Alan: /* Deciding which reports to produce */

2016-10-24T20:06:11Z

Deciding which reports to produce

← Older revision		Revision as of 20:06, 24 October 2016
Line 76:		Line 76:
	such an extent that the listing becomes unwieldy and overwhelming		such an extent that the listing becomes unwieldy and overwhelming
	to work with.		to work with.

			In theory you can suppress the INFO report but there's no good reason to do it: The INFO report (one of the defaults) describes the Model 204 environment, and also the selection criteria for the report and the sampling characteristics of the SirTune data collection. Without this information it is difficult to make sense of the specific performance reports.

	===Sample data set restrictions===		===Sample data set restrictions===

JAL: misc formatting

2016-10-24T16:23:17Z

misc formatting

Show changes

Alan: /* The SirTune reports */

2016-10-24T15:40:02Z

The SirTune reports

← Older revision		Revision as of 15:40, 24 October 2016
Line 128:		Line 128:
	SirTune stopped because End of data in sample dataset</p>		SirTune stopped because End of data in sample dataset</p>

	The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect~~, the~~ <em>number of sample skipped</em>, usually ~~because the user~~ specified a narrower ~~timespan~~ than ~~was represented in~~ the full journal~~, and~~ the <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).		The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect. A non-zero <em>number of sample skipped</em> is usually due to a specified timespan being narrower than the full journal; the skipped samples are outside the selected date/time range. The <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).

	The rest of the info shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the start of journal, time brackets for this report, the <var class="product">SirTune</var> version and the reason data collection stopped - <em>End of sample dataset</em> indicates normal completion.		The rest of the info shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the start of journal, time brackets for this report, the <var class="product">SirTune</var> version and the reason data collection stopped - <em>End of sample dataset</em> indicates normal completion.

Alan: /* INFO reports */

2016-10-24T15:37:13Z

INFO reports

← Older revision		Revision as of 15:37, 24 October 2016
Line 104:		Line 104:
	<p class="syntax">REPORT INFO		<p class="syntax">REPORT INFO
	</p>		</p>
	The <code>INFO</code> report provides environmental information about the <var class="product">Model 204</var> ONLINE program and <var class="product">SirTune</var> data collection settings used in producing		The <code>INFO</code> report provides environmental information about the <var class="product">Model 204</var> ONLINE program and <var class="product">SirTune</var> data collection settings used in producing the sample data set.
	the sample data set.
	This report includes settings of key <var class="product">Model 204</var> parameters (<var>NUSERS</var>, <var>NSERVS</var>, <var>NJBUFF</var>, etc.) and <var class="product">SirTune</var> parameters (sampling interval, COLLECT settings, etc.).		This report includes settings of key <var class="product">Model 204</var> parameters (<var>NUSERS</var>, <var>NSERVS</var>, <var>NJBUFF</var>, etc.) and <var class="product">SirTune</var> parameters (sampling interval, COLLECT settings, etc.).

Line 129:		Line 128:
	SirTune stopped because End of data in sample dataset</p>		SirTune stopped because End of data in sample dataset</p>

	The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall ~~length of the~~ timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect, the <em>number of sample skipped</em>, usually because the user specified a narrower timespan than was represented in the full journal, and the <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).		The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect, the <em>number of sample skipped</em>, usually because the user specified a narrower timespan than was represented in the full journal, and the <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).

	The rest of the info shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the start of journal, time brackets for this report, the <var class="product">SirTune</var> version and the reason data collection stopped - <em>End of sample dataset</em> indicates normal completion.		The rest of the info shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the start of journal, time brackets for this report, the <var class="product">SirTune</var> version and the reason data collection stopped - <em>End of sample dataset</em> indicates normal completion.

Alan: /* INFO reports */

2016-10-24T13:27:31Z

INFO reports

← Older revision		Revision as of 19:53, 8 August 2017
Line 26:		Line 26:

	===Use REPORT or <report> to specify which reports to produce===		===Use REPORT or <report> to specify which reports to produce===
	If not suppressed with the [[SirTune ~~Report Generator configuration~~#~~REPort report_desc \| NODEFAULT~~\|REPORT NODEFAULT]] statement, the reporting module always produces a default set of reports.		If not suppressed with the [[SirTune report generation#report\|REPORT NODEFAULT]] statement, the reporting module always produces a default set of reports.
	Additional reports are requested with the REPORT statement.		Additional reports are requested with the REPORT statement.

Line 130:		Line 130:
	<li>A non-zero <code>Number of samples skipped</code> is usually due to a specified time span being narrower than that represented in the full journal; the skipped samples are outside the selected date/time range. </li>		<li>A non-zero <code>Number of samples skipped</code> is usually due to a specified time span being narrower than that represented in the full journal; the skipped samples are outside the selected date/time range. </li>

	<li>The <code>Number of samples discarded</code> reports samples discarded when more than [[SirTune ~~Report Generator configuration~~#MAXDelay max_msec\|MAXDELAY]] milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the Online is not getting the resources it needs — it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample. </li>		<li>The <code>Number of samples discarded</code> reports samples discarded when more than [[SirTune report generation#MAXDelay max_msec\|MAXDELAY]] milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the Online is not getting the resources it needs — it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample. </li>

	<li>The rest of the report shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the journal's starting time, time brackets for this report, the <var class="product">SirTune</var> version, and the reason data collection stopped (<code>End of data in sample dataset</code> indicates normal completion). </li>		<li>The rest of the report shows the user's data collection settings (useful if you request a report and find that the necessary data is not in the collection for that report), the journal's starting time, time brackets for this report, the <var class="product">SirTune</var> version, and the reason data collection stopped (<code>End of data in sample dataset</code> indicates normal completion). </li>
Line 193:		Line 193:
	If not running the MP/204 feature or running the feature with 0 subtasks, CSECT is equivalent to CSECTM, and CSECTS is always 0.		If not running the MP/204 feature or running the feature with 0 subtasks, CSECT is equivalent to CSECTM, and CSECTS is always 0.
	<blockquote class="note">		<blockquote class="note">
	<b>Note:</b> If using XML for the parameters ([[SirTune ~~Report Generator configuration~~#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different CSECT report variations: specify a "task=maintask" or "task=subtask" attribute for a "type=csect" report to invoke, repectively, a <code>CSECTM</code> or a <code>CSECTS</code> report.		<b>Note:</b> If using XML for the parameters ([[SirTune report generation#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different CSECT report variations: specify a "task=maintask" or "task=subtask" attribute for a "type=csect" report to invoke, repectively, a <code>CSECTM</code> or a <code>CSECTS</code> report.
	<p>		<p>
	For example, to get a <code>CSECTM</code> report: </p>		For example, to get a <code>CSECTM</code> report: </p>
Line 223:		Line 223:
	<p class="code">REPORT CSECT TOTAL CHUNK 512 CHUNK 64		<p class="code">REPORT CSECT TOTAL CHUNK 512 CHUNK 64
	</p>		</p>
	<p class="note"><b>Note:</b> You can use the [[SirTune ~~Report Generator configuration~~#mapcore\|MAPCORE]] statement in the report configuration input to specify that instructions outside of the loaded <var class="product">Model 204</var> module are to be treated as a "CSECT," allowing analysis of CPU usage in the entire address space.		<p class="note"><b>Note:</b> You can use the [[SirTune report generation#mapcore\|MAPCORE]] statement in the report configuration input to specify that instructions outside of the loaded <var class="product">Model 204</var> module are to be treated as a "CSECT," allowing analysis of CPU usage in the entire address space.
	</p>		</p>

Line 276:		Line 276:

	The <code>QUADC</code> report breaks down all CPU usage by quad and the CSECTs. Since the breakdown is a CSECT-level breakdown, the		The <code>QUADC</code> report breaks down all CPU usage by quad and the CSECTs. Since the breakdown is a CSECT-level breakdown, the
	[[SirTune ~~Report Generator configuration~~#mpvirt\|MPVIRT]] configuration parameter has no effect on the QUADCM and QUADCS reports — only the		[[SirTune report generation#mpvirt\|MPVIRT]] configuration parameter has no effect on the QUADCM and QUADCS reports — only the
	real task on which a request was running is used to distinguish CSECTS and CSECTM.		real task on which a request was running is used to distinguish CSECTS and CSECTM.

Line 282:		Line 282:
	the feature with 0 subtasks, QUADC is equivalent to QUADCM, and QUADCS is always 0.		the feature with 0 subtasks, QUADC is equivalent to QUADCM, and QUADCS is always 0.

	<blockquote class="note"><b>Note:</b> If using XML for the parameters ([[SirTune ~~Report Generator configuration~~#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different QUADC report variations: specify a "task=maintask" or "task=subtask" attribute for a "type=quadc" report to invoke, repectively, a QUADCM or a QUADCS report.		<blockquote class="note"><b>Note:</b> If using XML for the parameters ([[SirTune report generation#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different QUADC report variations: specify a "task=maintask" or "task=subtask" attribute for a "type=quadc" report to invoke, repectively, a QUADCM or a QUADCS report.
	<p>		<p>
	For example, to get a <code>QUADCM</code> report:</p>		For example, to get a <code>QUADCM</code> report:</p>
Line 314:		Line 314:
	<p class="code">REPORT QUADC TOTAL CHUNK 512 CHUNK 64		<p class="code">REPORT QUADC TOTAL CHUNK 512 CHUNK 64
	</p>		</p>
	<p class="note"><b>Note:</b> The [[SirTune ~~Report Generator configuration~~#mapcore\|MAPCORE]] statement in the report configuration input specifies that instructions outside of the loaded <var class="product">Model 204</var> module		<p class="note"><b>Note:</b> The [[SirTune report generation#mapcore\|MAPCORE]] statement in the report configuration input specifies that instructions outside of the loaded <var class="product">Model 204</var> module
	should be treated as a "CSECT," allowing analysis of CPU usage in the		should be treated as a "CSECT," allowing analysis of CPU usage in the
	entire address space.		entire address space.
Line 329:		Line 329:
	report buffer time, etc. In addition, the <code>REPSTAT</code> report provides information on above-the-line (31 bit) and below-the-line (24 bit) storage usage.</p>		report buffer time, etc. In addition, the <code>REPSTAT</code> report provides information on above-the-line (31 bit) and below-the-line (24 bit) storage usage.</p>

	<p class="note"><b>Note:</b> This report is only of interest if the performance or storage usage of SIRTUNER is a concern. It is not supported in <var class="product">SirTune</var> 7.2 and later (using the SIRTUNEREPORT <var class="product">SOUL</var> program), and a <code>repstat</code> keyword is <i>not</i> supported as a report type option in the XML format for specifying report configuration parameters ([[SirTune ~~Report Generator configuration~~#templt\|A template for the XML input]]).		<p class="note"><b>Note:</b> This report is only of interest if the performance or storage usage of SIRTUNER is a concern. It is not supported in <var class="product">SirTune</var> 7.2 and later (using the SIRTUNEREPORT <var class="product">SOUL</var> program), and a <code>repstat</code> keyword is <i>not</i> supported as a report type option in the XML format for specifying report configuration parameters ([[SirTune report generation#templt\|A template for the XML input]]).
	</p>		</p>

Line 587:		Line 587:

	The <code>WHATC</code> report breaks down all CPU usage by <var class="product">Model 204</var> activity and CSECTs. Since the breakdown is a CSECT-level breakdown, the setting of the MPVIRT parameter		The <code>WHATC</code> report breaks down all CPU usage by <var class="product">Model 204</var> activity and CSECTs. Since the breakdown is a CSECT-level breakdown, the setting of the MPVIRT parameter
	([[SirTune ~~Report Generator configuration~~#mpvirt\|MPVirt]]) has no effect on the <code>WHATCM</code> and <code>WHATCS</code> reports — only the real task on which a request was running is used to distinguish CSECTS and CSECTM.		([[SirTune report generation#mpvirt\|MPVirt]]) has no effect on the <code>WHATCM</code> and <code>WHATCS</code> reports — only the real task on which a request was running is used to distinguish CSECTS and CSECTM.

	When running the [[MP/204]] feature, the WHATCM report breaks down maintask CPU usage by activity and CSECT, and the WHATCS report breaks down subtask CPU usage		When running the [[MP/204]] feature, the WHATCM report breaks down maintask CPU usage by activity and CSECT, and the WHATCS report breaks down subtask CPU usage
Line 593:		Line 593:

	<blockquote class="note">		<blockquote class="note">
	<b>Note:</b> If using XML for the parameters ([[SirTune ~~Report Generator configuration~~#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different WHATC report variations: specify a <code>task=maintask</code> or <code>task=subtask</code> attribute for a <code>type=whatc</code> report to invoke, repectively, a <code>WHATCM</code> or a <code>WHATCS</code> report.		<b>Note:</b> If using XML for the parameters ([[SirTune report generation#xmlrpti\|Using XML input for report configuration]]), a single convention can handle these different WHATC report variations: specify a <code>task=maintask</code> or <code>task=subtask</code> attribute for a <code>type=whatc</code> report to invoke, repectively, a <code>WHATCM</code> or a <code>WHATCS</code> report.
	<p>		<p>
	For example, to get a <code>WHATCS</code> report:</p>		For example, to get a <code>WHATCS</code> report:</p>
Line 624:		Line 624:
	<p class="code">REPORT WHATC TOTAL CHUNK 512 CHUNK 64		<p class="code">REPORT WHATC TOTAL CHUNK 512 CHUNK 64
	</p>		</p>
	<p class="note"><b>Note:</b> The [[SirTune ~~Report Generator configuration~~#mapcore\|MAPCORE]] statement in the report configuration input specifies that instructions outside of the loaded <var class="product">Model 204</var> module should be treated as a "CSECT," allowing analysis of CPU usage in the entire address space.		<p class="note"><b>Note:</b> The [[SirTune report generation#mapcore\|MAPCORE]] statement in the report configuration input specifies that instructions outside of the loaded <var class="product">Model 204</var> module should be treated as a "CSECT," allowing analysis of CPU usage in the entire address space.
	</p>		</p>

Line 630:		Line 630:
	Many reports produce a listing of entities ranked in order of the number		Many reports produce a listing of entities ranked in order of the number
	of samples for which data was found. The number of entities listed		of samples for which data was found. The number of entities listed
	on these reports is either 50 or the value indicated on the last [[SirTune ~~Report Generator configuration~~#TOP num_top\|TOP		on these reports is either 50 or the value indicated on the last [[SirTune report generation#TOP num_top\|TOP statement]] before the REPORT statement. Thus, the following statement would list the top 50 evaluating procedures if no TOP statements appear in SIRTUNEI:
	statement]] before the REPORT statement. Thus, the following
	statement would list the top 50 evaluating procedures if no TOP statements
	appear in SIRTUNEI:
	<p class="code">REPORT STATE RUNG EVAL		<p class="code">REPORT STATE RUNG EVAL
	</p>		</p>

← Older revision		Revision as of 13:27, 24 October 2016
Line 115:		Line 115:

	<p class="code"> Sampling Rate = 10.00 seconds		<p class="code"> Sampling Rate = 10.00 seconds
	Number of samples processed = 13359		Number of samples processed = 13359
	Number of samples missed = 0		Number of samples missed = 0
	Number of samples skipped = 13347		Number of samples skipped = 13347
	Number of samples discarded = 3 (MAXDELAY = 10)		Number of samples discarded = 3 (MAXDELAY = 10)
	Number of samples accepted = 9		Number of samples accepted = 9
	States collected = RUNG REDY BLKIN BLKON		States collected = RUNG REDY BLKIN BLKON
	Extra data collected = DISKIO CFR		Extra data collected = DISKIO CFR
	Options =		Options =
	Job start time = Sunday, 23 October 2016 00:18:33		Job start time = Sunday, 23 October 2016 00:18:33
	First sample processed = Monday, 24 October 2016 13:23:20		First sample processed = Monday, 24 October 2016 13:23:20
	Last sample processed = Monday, 24 October 2016 13:25:10		Last sample processed = Monday, 24 October 2016 13:25:10
	SIRTUNE version = 8.3		SIRTUNE version = 8.3
	SirTune stopped because End of data in sample dataset</p>		SirTune stopped because End of data in sample dataset</p>

	The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall length of the timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect, the <em>number of sample skipped</em>, usually because the user specified a narrower timespan than was represented in the full journal, and the <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).		The <em>sampling rate</em> times the <em>number of samples processed</em> will give you the overall length of the timespan of the journal. <em>Samples missed</em> reflects the count of samples <var class="product">SirTune</var> failed to collect, the <em>number of sample skipped</em>, usually because the user specified a narrower timespan than was represented in the full journal, and the <em>number of samples discarded</em>: Samples get discarded when more than MAXDELAY milliseconds pass between the time <var class="product">SirTune</var> wanted to collect the sample and when it actually did. A significant number of discarded samples might indicate the online is not getting the resources it needs (it certainly indicates that <var class="product">SirTune</var> was not getting the resources it needed when it tried to take a sample).