HP NonStop G-Series - Manual (Page 49)

Configuring and Running Measurements
Measure User’s Guide — 520560-003
3 -7
Stopping a Measurement
This command starts a measurement at 9:00 a.m., ends the measurement at 5:00
p.m., and specifies a 30-minute collection interval:
4+ START MEASUREMENT $PERF.DATA.NOV5, FROM 9:00, TO 17:00,&
4& INTERVAL 30 MINUTES
Using a collection interval does not cause counters to be reset during a measurement.
Counter values are always accumulated for the entire measurement.
Use a collection interval only when you need a detailed view of system performance. A
collection interval can increase Measure overhead and the size of the data file. The
shorter the interval and the longer the measurement, the higher the overhead.
Stopping a Measurement
When a measurement stops:
1. MEASMON notifies all active MEASCTL processes that the command was issued.
2. The MEASCTL processes write ending records to the data file, deallocate the
counter records, perform some cleanup work, and notify MEASMON.
3. MEASMON writes wrap-up information in the data file and breaks the connection.
If you use the FROM-FOR, FROM-TO, or FOR clauses in the START
MEASUREMENT command, the measurement stops automatically at the specified
time.
If you have not used these clauses or if you choose to stop a measurement before the
specified time, you must use the STOP MEASUREMENT command. To use this
command, you must have the same user ID as the process that started the
measurement or be a super-group user (255,
n ).
You must also name the data file associated with the measurement configuration in the
STOP command:
4+ STOP MEASUREMENT $DATA.PERF.NOV05
When a measurement is stopped using this command, an ADD MEASUREMENT
operation is performed automatically on the data file so you can access it. To stop a
measurement without accessing its data file, use the NO ADD option of the STOP
MEASUREMENT command. For example:
4+ STOP MEASUREMENT $DATA.PERF.NOV05, NO ADD
5+ EXIT
10>
Note. On systems running G-series RVUs, some data files might be smaller than the files for
comparable measurements on systems running D-series RVUs. The difference is due to a
change in how MEASCTL writes data records when there is a collection interval. The
difference is most noticeable in large measurements, especially those measuring all FILE and
DISCOPEN entities.