2 schedule, 3 measurement hours, Schedule – HP 3PAR System Reporter Software User Manual
Page 281: Measurement hours, Es (see

9.9
Configuring Adaptive Optimization
System Reporter 2.8
3PAR System Reporter User’s Guide
9.3.2 Schedule
The schedule consists of three components: dates, weekdays and hours. You can choose
multiple values of each of these components to create a schedule for when each adaptive
optimization configuration executes.
9.3.3 Measurement Hours
You can specify the number of hours that you want to consider in order to determine the
activity level of regions. Control of the measurement duration is important especially for
applications whose performance is not uniformly important throughout the day.
For example, consider an application whose performance is important only during the first few
hours of a business day (Monday through Friday, 8 am through 11 am) and then not
particularly important throughout the rest of the day, though not necessarily idle the rest of
the day. If we measure the application throughout the day, the tiering will consider the
performance during times that are not important and as a result the performance during the
important times of the day may not be optimal. We can achieve optimal results by scheduling
adaptive optimization execution for 11 am Monday through Friday with a measurement
interval of 3 or 4 hours. That way only performance measurements during the important
period for the application will be considered.
NOTE: Adaptive optimization configurations may be scheduled to run at intervals
that are shorter than their measurement hours (see
page 9.9). However, regions that have been moved are not considered in the
analysis for subsequent iterations until at least the measurement interval has
expired.
CAUTION: There is single regionmover process for each InServ array, and it
completes analysis and data movement for all the adaptive optimization
configurations scheduled for the current hour before proceeding to the next
hour. If the time taken to complete the current configurations is so long that the
hour is past the execution time for the configurations scheduled next, it may skip
those configurations. You should therefore ensure that configurations are either
executed together or sufficiently spaced.