Using the Notification Server's Server Performance Report

book

Article ID: 179896

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

 

Resolution

Question

After running the NS server performance report, how do I use the report result to understand the NS?

Answer
The Notification Server's Server Performance Report provides valuable information on determining load, trends, and possible configuration problems. 

Use the server performance.xml and import in the Reports section of the NS console, preferably in a custom folder.

Starting the report, select Run this Report.

 

The "Days" defaults to 1 day of data from the NS; it is recommended to use the default. If multiple days are used, i.e. greater than 1, then all information from the report is a summation of all the days and may not be useful in determining trends or making changes to the NS configuration. The best use of this report is to run it on a regular schedule to allow for determining trends and preventing server utilization issues.




After clicking Refresh, the output is below.




There are four tasks; each will be discussed to help in understanding the data provided.

Task

Scheduled Tasks



Using the results from the report, let's discuss each row starting with Scheduled Tasks.  According to this report there were 1321 operations on this NS taking a total of 543.79 minutes, each averaging 24699 ms with 0 errors and totaling of 537 distinct computers for all the operations. Double-clicking the Scheduled Tasks row will give detailed information about the 1321 operations.
 
Going to the next screen below:



Taking a subset of all the operations, let's discuss the highlighted operations as an example how this report is useful. Reviewing in some detail the two operations, "Policy Changed Collections Updated Schedule" and "Collection Delta Update Schedule."  The Policy Changed Collections Updated Schedule was executed 47 times, averaging 96996 ms per execution and requiring a 75.98 minutes total of the last 24 hours. The Collection Delta Updated Schedule was executed 45 times, averaging 358691 ms per execution and requiring a 269.02 minutes total of the last 24 hours.   

With this information, let's review the Notification Server settings for these two operations. The order of execution is "Collection Delta Update Schedule" then "Policy Changed Collections Updated Schedule." So in the NS Console > Server Settings > Notification Server Settings > Automatic Collection Updating, both operations are scheduled to start at the same time as shown below.


 
The report information shows for the past 24 hours the average time for the "Collection Delta Update Schedule" to complete is 358691 ms or about 6 minutes to complete on average. Using this information the start time should be adjusted to prevent these operations running at the same time, which can cause performance issues. To resolve, simply change the start time of "Policy Changed Collection Update Schedule" from starting at 2:00:00 a.m. to 2:15:00 a.m.

Message Processing




The next task, Message Processing, shows there were 78,261 operations performed by the NS in the last 24 hours, taking 109.09 minutes, averaging 83 ms with 449 errors and totaling 3,328 distinct computers for all the operations. 

Double-clicking the Message Processing row, will give detail information about the 78,261 operations.
 
Going to the next screen below:



Taking a subset of all the operations, lets use the highlighted operation as an example. The Inv Basic Inventory Item had 6,092 events, each averaging 496 ms, requiring a total of 50.38 minutes with 1 distinct computer with no errors.   

Now let's check the Notification Server settings for this operation. The report information shows for the past 24 hours the Inv Basic Inventory Item took 496 ms per event to complete. The setting that affect this report is in the screen below.



The Advance Notification Server Settings from the NS shown above show all the events are checked. However, depending on the requirements in your environments this may be unnecessary. Another configuration setting Altiris Agent Configuration that can impact the NS server. Let's review the screen below.



The the Agent Basic Settings show the "Request new configuration information every" is set at 1 hour that can be changed, depending on your requirements, to 4 hours and the "Send basic inventory every" from 12 hours to daily. In a large environment these settings can reduce the NS load.

Client Config Requests



The next task, Client Config Requests, shows there were 17,825 operations performed by the NS in the last 24 hours, taking 61.51 minutes, averaging 207 ms with 16 errors and totaling 3,355 distinct computers for all the operations. 

Double clicking the Client Config Requests row, will give detail information about the 78,261 operations.
 
Going to the next screen below:



Taking a subset of the tasks, let's discuss the highlighted computer as an example how this report is useful. The W2KPRO1 computer made 6 requests, each averaging 90 ms, taking a total of 0.55 seconds, making its last request at 4/11/2006 4:21:15 PM, with 0 changes and 3 changed and there were 3 errors.

This information can be extremely useful if the NS is experiencing utilization problems, by checking for computers that have excessive number of requests or the Avg is higher than other computers or the number of Errors all could be used to flag possible problems that will help in diagnosing issues. 

If you double-click on the highlight name, the report will drill down and give detailed information about the computer as shown below.





Report Execution




The next task, Report Execution, shows there were 65 operations on this NS taking a total of 0.48 minutes, each averaging 7446 ms with 1 errors and totaling of 17 distinct machines for all the operations. Double-clicking the Report Execution row will give detail information about the 65 operations.
 
Going to the next screen below:



Let's discuss the highlighted report "Microsoft Software Update Compliance by Bulletin" as an example how this report is useful. The "Microsoft Software Update Compliance by Bulletin" was executed 4 times, each report averaged 72750 ms to run, taking a total of 0.29 minutes and there were 0 errors. There is no problem shown in this report.  However, if a report is being executed excessively, consuming large amount of time or reports high number of errors, this would be a report that needs to be researched.

This has been a brief overview of the Server Performance Report, but this should help in understanding and using the information for Notification Server tuning and identifying areas that drastically affect the server performance.

Attachments

Server Performance.zip get_app
Server Performance.zip get_app