Neoview Workload Management Services Guide (R2.4)

3 Configuring Services
• “What Are Services?” (page 27)
• “Configuring the WMS System Configuration” (page 28)
• “Configuring User-Defined Services” (page 29)
What Are Services?
Services are a mechanism in WMS to enable you to prioritize query workloads on a Neoview
platform and distribute available workload resources. WMS has these types of services:
• “System Service” (page 27)
• “Default Service” (page 27)
• “User-Defined Services” (page 27)
Each service in WMS has a priority and system resource thresholds associated with it:
• “Service Priority” (page 27)
• “System Resource Thresholds” (page 27)
System Service
WMS has a built-in system configuration, the SYSTEM service, which defines thresholds for the
Neoview platform. The SYSTEM service does not handle incoming queries, as other services in
WMS do. However, WMS applies threshold values from the SYSTEM service as default values
when you do not specify those threshold values when creating a service. You can alter the
threshold values of the SYSTEM service but cannot delete this service. For more information,
see “Configuring the WMS System Configuration” (page 28).
Default Service
By default, WMS uses the default service, HP_DEFAULT_SERVICE, to handle incoming queries.
As an administrator, you can alter the thresholds of HP_DEFAULT_SERVICE but cannot delete
this service.
User-Defined Services
As an administrator, you can define your own services to distribute query workloads according
to your workload management strategy. You may add up to 255 user-defined services in addition
to the predefined HP_DEFAULT_SERVICE and SYSTEM services on a Neoview platform. For
more information, see “Configuring User-Defined Services” (page 29).
Service Priority
The priority of a service determines when the queries associated with the service are executed
in relation to queries associated with other services. If queries from low and high priority services
are waiting to execute, the high priority queries execute before the low priority queries, provided
that the system resource usage does not reach its limits.
System Resource Thresholds
The system resource thresholds, MAX_CPU_BUSY and MAX_MEM_USAGE, of a service influence
whether incoming queries associated with the service start executing immediately or are put in
a waiting queue. To determine available CPU and memory resources for the Neoview platform,
WMS looks at a moving average every five seconds for six intervals of CPU busy and takes a
snapshot every five seconds of memory usage on the Neoview platform. When the system
resource usage reaches the threshold limits for the service, WMS puts incoming queries associated
with the service into a waiting queue.
What Are Services? 27