Policy and Rule Descriptions
Policies Set in WebQoS
Concurrent sessions means the total number of sessions that have not expired (based on the configuration of the advanced features discussed in “Modifying Session Timeouts” on page 74) and are possibly active. This number does not indicate the total number of sessions currently active on the system.
•Support at most NUMBER concurrent sessions
This SLO lets you support a specific NUMBER (for example, 1000) of concurrent sessions. The request classification CLASS information is not supported.
Concurrent sessions means the total number of sessions that have not expired (based on the configuration of the advanced features discussed in “Modifying Session Timeouts” on page 74) and are possibly active. This number does not indicate the total number of sessions currently active on the system.
Service Level Objectives for the Service
WebQoS offers the following SLO at the Service Level which provides you with an aggregate session count for the entire service.
•Support at most NUMBER concurrent sessions
This SLO lets you support a specific NUMBER (for example, 1000) of concurrent sessions. The request classification CLASS information is not supported.
Concurrent sessions means the total number of sessions that have not expired and are possibly active.
Threshold Policies
Threshold policies are “internal” measures used to ensure that your system is operating in a reasonable performance range and does not get overloaded. They put limits on CPU load and queue depth.
If CPU load gets too high, your server may get into a thrashing state, causing few or possibly no requests to be satisfied in a timely fashion. If WebQoS queues begin to grow abnormally, this may signal a problem with your web server or an application/database process that it relies upon.
The threshold policies supported by WebQoS are:
Appendix A | 159 |
