Neoview Workload Management Services Guide (R2.4)

WAIT_TIMEOUT 720,
HOLD_TIMEOUT 1440,
PLAN, TEXT,
COMMENT "Created by DBA on 5/14/2009";
ADD SERVICE service2
PRIORITY MEDIUM,
MAX_CPU_BUSY 75,
MAX_MEM_USAGE 60,
EXEC_TIMEOUT 240,
WAIT_TIMEOUT 1400,
PLAN, TEXT,
COMMENT "Created by DBA on 5/14/2009";
ADD SERVICE service3
PRIORITY LOW,
MAX_CPU_BUSY 55,
MAX_MEM_USAGE 40,
MAX_ROWS_FETCHED 2000,
PLAN, TEXT,
COMMENT "Created by DBA on 5/14/2009";
Setting lower system resource thresholds for lower priority services restricts the number of
executing queries associated with lower priority services and enables more queries associated
with higher priority services to execute on the Neoview platform. For example, for a lower
priority service, suppose you set the CPU busy to 55% and the memory usage to 40%. Incoming
queries associated with the lower priority service automatically go into the waiting queue when
the CPU busy and maximum memory usage exceed the service thresholds of 55% and 40%,
respectively. This strategy might be useful for preventing lower priority queries, such as from
reporting applications or ad-hoc queries, from consuming the system resources needed by higher
priority queries.
Setting the Active Time of the Service
The active time of a service is a time range when the service can accept incoming queries. A
service is in the ACTIVE state during its active period. Outside of its active period, the service
is in the HOLD state.
Outside the active time range, a service cannot execute incoming queries associated with the
service. If a query is still executing in the service when the end time is reached, WMS allows the
query to continue executing outside the active time range. However, WMS rejects any incoming
queries associated with the service if they occur outside the active time range. For example, if
you specify an active time of 15:00 to 18:00, WMS enables queries associated with the service to
start executing between the hours of 15:00 to 18:00 but rejects any queries associated with the
service that try to execute outside the active time of 15:00 to 18:00.
By default, the active time is from 00:00 through 24:00. To change the active time, specify the
start and end times during which you want the service to execute queries. The start or end time,
hh:mm, is in hours (hh) and minutes (mm). Currently, the active time cannot span more than one
day.
For example, these ADD SERVICE commands define services that have the same priority but
accept incoming queries at different times. SERVICE1 accepts incoming queries between 8:00
a.m. and midnight, and SERVICE4 accepts incoming queries between midnight and 7:59 a.m.:
ADD SERVICE service1
PRIORITY HIGH,
MAX_CPU_BUSY 95,
MAX_MEM_USAGE 80,
ACTIVE 08:00 TO 24:00,
EXEC_TIMEOUT 120,
WAIT_TIMEOUT 720,
HOLD_TIMEOUT 1440,
32 Configuring Services