/usr/share/GNUstep/Documentation/Performance/GSThroughput.gsdoc is in libperformance-dev 0.5.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 | <?xml version="1.0"?>
<!DOCTYPE gsdoc PUBLIC "-//GNUstep//DTD gsdoc 1.0.3//EN" "http://www.gnustep.org/gsdoc-1_0_3.dtd">
<gsdoc base="GSThroughput">
<head>
<title>GSThroughput class documentation</title>
<author name="Richard Frith-Macdonald">
<email address="rfm@gnu.org">
rfm@gnu.org
</email>
</author>
<version>33278</version>
<date>2011-06-11 15:41:59 +0100 (Sat, 11 Jun 2011)</date>
<copy>2005-2008 Free Software Foundation, Inc.</copy>
</head>
<body>
<front><contents /></front>
<chapter>
<heading>
Software documentation for the GSThroughput class
</heading>
<class name="GSThroughput" super="NSObject">
<declared>GSThroughput.h</declared>
<desc>
<p>
The GSThroughput class is used maintain statistics
about the number of events or the duration of
operations in your software.
</p>
<p>
For performance reasons, the class avoids locking and
you must ensure that an instance of the class is only
ever used by a single thread (the one in which it was
created). You are responsible for ensuring that a
run loop runs in each thread in which you use an
instance, so that stats can be updated for that
thread every second.
</p>
<p>
You create an instance of the class for each
event/operation that you are interested in
monitoring, and you call the
<ref type="method" id="-add:">
-add:
</ref>
or
<ref type="method" id="-addDuration:">
-addDuration:
</ref>
method to record events. <br /> For duration
logging, you may also use the
<ref type="method" id="-startDuration:">
-startDuration:
</ref>
and
<ref type="method" id="-endDuration">
-endDuration
</ref>
methods to handle adding of the amount of time
taken between the two calls.
</p>
<p>
To dump a record of the gathered statistics, you may
call the
<ref type="method" id="-description">
-description
</ref>
method of an instance or the class
<ref type="method" id="+description">
+description
</ref>
method to dump statistics for all instances in the
current thread. <br /> If you need to gather a
record for all the threads you use, you must
generate a dump in each thread and combine the
results.
</p>
<p>
To be notified of statistics at the end of each minute,
you may call the
<ref type="method" id="-enableNotifications:">
-enableNotifications:
</ref>
method for an instance. The notifications are
generated in the thread that instance belongs to.
</p>
</desc>
<ivariable type="void*" name="_data" validity="protected">
<desc>
<em>Warning</em> the underscore at the start of the
name of this instance variable indicates that, even
though it is not technically <em>private</em>, it is
intended for internal use within the package, and
you should not use the variable in other code.
</desc>
</ivariable>
<method type="NSArray*" factory="yes">
<sel>allInstances</sel>
<desc>
Return all the current throughput measuring objects
in the current thread. NB. This does not return
instances from other threads.
</desc>
</method>
<method type="NSString*" factory="yes">
<sel>description</sel>
<desc>
Return a report on all GSThroughput instances in the
current thread... <br /> This calls the
<ref type="method" id="-description" class="GSThroughput">
[GSThroughput -description]
</ref>
method of the individual instances to get a report
on each one. <br /> The results are ordered
alphabetically by name of the instances (an
instance without a name is treated as having an
empty string as a name).
</desc>
</method>
<method type="void" factory="yes">
<sel>setTick:</sel>
<arg type="BOOL">aFlag</arg>
<desc>
Instructs the monitoring system to use a timer at
the start of each second for keeping its idea of the
current time up to date. This timer is used to call
the <ref type="method" id="+tick">+tick</ref> method in
the current thread. <br /> Passing a value of
<code>NO</code> for <var>aFlag</var> will turn off
the timer for the current thread. <br /> For the timer
to work, the thread's runloop must be running. <br />
Keeping the notion of the current time up to date
is important for instances configured to record stats
broken down over a number of periods, since the
periodic breakdown must be adjusted each second.
</desc>
</method>
<method type="void" factory="yes">
<sel>tick</sel>
<desc>
Updates the monitoring system's notion of the
current time for all instances associated with the
current thread. <br /> This should be called at the
start of each second (or more often) if you want an
accurate breakdown of monitoring by the second.
<br /> If you don't want to call this yourself, you
can call
<ref type="method" id="+setTick:">
+setTick:
</ref>
to have it called automatically. <br /> If you are not
using any instances of the class configured to
maintain a breakdown of stats by periods, you do
not need to call this method.
</desc>
</method>
<method type="void">
<sel>add:</sel>
<arg type="unsigned">count</arg>
<desc>
Add to the <var>count</var> of the number of
transactions for the receiver. <br /> You may
use this method only if the receiver was initialised
with duration logging turned off.
</desc>
</method>
<method type="void">
<sel>add:</sel>
<arg type="unsigned">count</arg>
<sel>duration:</sel>
<arg type="NSTimeInterval">length</arg>
<desc>
Adds a record for multiple events of the specified
<em>total</em> duration. <br /> This is useful where
you know a lot of similar events have completed in a
particular period of time, but can't afford to
measure the duration of the individual events
because the timing overheads would be too great.
<br /> You may use this method only if the receiver
was initialised with duration logging turned on.
</desc>
</method>
<method type="void">
<sel>addDuration:</sel>
<arg type="NSTimeInterval">length</arg>
<desc>
Adds a record for a single event of the specified
duration. <br /> You may use this method only if
the receiver was initialised with duration logging
turned on.
</desc>
</method>
<method type="NSString*">
<sel>description</sel>
<desc>
Returns a string describing the status of the
receiver. <br /> For an instance configured to
maintain a periodic breakdown of stats, this
reports information for the current second, all
seconds in the current minute, all minutes in the
current period, and all periods in the configured
number of periods. <br /> For an instance configured
with no periodic breakdown, this produces a
<strong>short</strong> summary of the total count
of events and, where durations are used, the maximum,
minimum and average duration of events.
</desc>
</method>
<method type="BOOL">
<sel>enableNotifications:</sel>
<arg type="BOOL">flag</arg>
<desc>
Sets a <var>flag</var> to say whether the receiver
will send GSThroughputNotification at the end of each
minute to provide information about statistics.
<br /> The method returnes the previous setting. The
initial setting is <code>NO</code>. <br /> The
notification object is the reciever, and the
user info dictionary contains some or all of the
following keys depending on how the receiver was
configured:
<deflist>
<term>GSThroughputCountKey</term>
<desc>
The number of events recorded (
<strong>unsigned</strong> integer number)
</desc>
<term>GSThroughputMaximumKey</term>
<desc>
The maximum event duration (<strong>double</strong>
floating point number)
</desc>
<term>GSThroughputMinimumKey</term>
<desc>
The minimum event duration (<strong>double</strong>
floating point number) or -1.0 if no events
occurred during the minute.
</desc>
<term>GSThroughputTimeKey</term>
<desc>
The time of the start of the minute (an NSDate)
</desc>
<term>GSThroughputTotalKey</term>
<desc>
The sum of event durations (<strong>double</strong>
floating point number)
</desc>
</deflist>
</desc>
</method>
<method type="void">
<sel>endDuration</sel>
<desc>
Ends duration recording for the current event started
by a matching call to the
<ref type="method" id="-startDuration:">
-startDuration:
</ref>
method. <br /> Calls to this method without a
matching call to
<ref type="method" id="-startDuration:">
-startDuration:
</ref>
are quietly ignored. This is useful if you wish to time
a function or method by starting/ending timing
before/after calling it, but also want the
function/method to be able to end timing of
itsself before it calls another function/method.
</desc>
</method>
<method type="void">
<sel>endDuration:</sel>
<arg type="unsigned">count</arg>
<desc>
Acts like
<ref type="method" id="-endDuration">
-endDuration
</ref>
but records the duration as a total for
<var>count</var> events (if <var>count</var> is zero
then this ends the interval started by the
corresponding
<ref type="method" id="-startDuration:">
-startDuration:
</ref>
call, but nothing is logged). <br /> This can be used
when recording multiple events where the overhead of
timing each event individually would be too great.
</desc>
</method>
<method type="id">
<sel>init</sel>
<desc>
Initialises the receiver for duration logging
(in the current thread only) for fifteen minute periods
over the last twentyfour hours.
</desc>
</method>
<method type="id" init="yes">
<sel>initWithDurations:</sel>
<arg type="BOOL">aFlag</arg>
<sel>forPeriods:</sel>
<arg type="unsigned">numberOfPeriods</arg>
<sel>ofLength:</sel>
<arg type="unsigned">minutesPerPeriod</arg>
<desc>
<p>
Initialises the receiver to maintain stats
(for the current thread only) over a particular time
range, specifying whether duration statistics are
to be maintained, or just event/transaction counts.
</p>
<p>
If the specified <var>numberOfPeriods</var> or
<var>minutesPerPeriod</var> is zero, only a running
total is maintained rather than a per-second
breakdown for the current minute and per minute
breakdown for the current period and period
breakdown for the number of periods.
</p>
<p>
If all instances in a thread are initialised with
<var>numberOfPeriods</var> or
<var>minutesPerPeriod</var> of zero, the
<ref type="method" id="+tick">
+tick
</ref>
method does not need to be called and
<ref type="method" id="+setTick:">
+setTick:
</ref>
should not be used.
</p>
</desc>
</method>
<method type="NSString*">
<sel>name</sel>
<desc>
Return the name of this instance (as set using
-setName:). <br /> This is used in the
<ref type="method" id="-description">
-description
</ref>
method and for ordering instances in the
<ref type="method" id="+description">
+description
</ref>
method.
</desc>
</method>
<method type="void">
<sel>setName:</sel>
<arg type="NSString*">name</arg>
<desc>
Sets the <var>name</var> of this instance.
</desc>
</method>
<method type="void">
<sel>startDuration:</sel>
<arg type="NSString*">name</arg>
<desc>
Starts recording the duration of an event. This must
be followed by a matching call to the
<ref type="method" id="-endDuration">
-endDuration
</ref>
method. <br /> The <var>name</var> argument is used
to identify the location of the call for
debugging/logging purposes, and you must
ensure that the string continues to exist up to the
point where
<ref type="method" id="-endDuration">
-endDuration
</ref>
is called, as the receiver will not retain it. <br />
You may use this method only if the receiver was
initialised with duration logging turned on.
<br /> Use of this method if the reciever does not
support duration logging or if the method has
already been called without a matching call to
<ref type="method" id="-endDuration">
-endDuration
</ref>
will cause an exception to be raised.
</desc>
</method>
</class>
</chapter>
<chapter>
<heading>GSThroughput constants</heading>
<p></p>
<constant type="NSString* const" name="GSThroughputCountKey">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
<constant type="NSString* const" name="GSThroughputMaximumKey">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
<constant type="NSString* const" name="GSThroughputMinimumKey">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
<constant type="NSString* const" name="GSThroughputNotification">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
<constant type="NSString* const" name="GSThroughputTimeKey">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
<constant type="NSString* const" name="GSThroughputTotalKey">
<desc>
<em>Description forthcoming.</em>
</desc>
</constant>
</chapter>
</body>
</gsdoc>
|