Insulate Users of the Same Application
Instructions to protect users of one application
from the performance impact of their peers
Not only do users need performance protection from bandwidth-hungry applications,
they also need protection from other users of their same application.
Consider the difference between these two scenarios:
- A Telnet user experiences poor performance because the total volume
of all FTP file downloads is too high.
- An FTP user waits forever because a high-capacity user is downloading
a huge file using FTP.
These instructions solve the second scenario, insulating all users of
a single application from each other. For a recommendation for the first
scenario, see Protect Critical
Application Performance.
Procedure:
-
Determine the maximum amount of bandwidth you'd like each
session of the application to be able to access. For example, you
might decide that each FTP session can access no more than 30 Kbps.
-
Determine
an appropriate priority for this application or traffic class.
-
Set
a rate policy on the traffic class you want to control. Use 0
guaranteed, with the priority and limit values you determined from
the previous steps.
For background information, see Policy
Overview.
|
