Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Service Manager Performance Considerations

    Like any application, Service Manager requires a certain amount of system resources. Consider the following guidelines to maximize the performance of Service Manager when delivering subscriber services:

    • Minimize service definitions—Use the minimum number of JunosE commands in a service definition to specify a service.
    • Reference objects in service definitions—Referencing commonly used objects is more resource-efficient than using unique objects for each subscriber (for example, using a subscriber’s IP address as a match criteria in a classifier list).
    • Preprovision frequently used services— Preprovisioning saves resources by requiring Service Manager to build a popular service only once. You then reuse the original service when you activate future subscriber service sessions. See Preprovisioning Service Sessions for details.
    • Capture volume statistics when needed—Repeatedly capturing volume statistics can waste resources.

    Published: 2014-08-20