Number of escalation policies that can successfully be processed using multiple threads

When 50,000 traps were sent to the trap adapters, the rate to compute the escalation of notifications at the Service Assurance Manager presentation server was measured for 5, 10, 20, and 50 escalation policies. For each escalation policy:

• The following path and levels were used: 1 path and 1 level, 5 paths and 3 levels, and 10 paths and 6 levels

• Each notification matches exactly one policy per path

  Note:

  Each escalation, path, and level action consisted of running a unique shell script that created an empty file in the local file system.

  Escalation policy benchmark results defines the escalation policy benchmarking results for SAM 8.0.

Table 1. Escalation policy benchmark results

Configurationpolicy/path/ level	Adapter Platform (OI)N/s	SAM-Aggregate N/s	SAM-Presentation N/s	Elapsed time in seconds	Queue growth	Memory start in KB	Memory end in KB	Delay in completion in seconds	Notification average escalation time in seconds	Time to load XML file
5/1/1	37.48	35.41	13.94	3587	2	264448	419432	0	0.1987	3.6
10/1/1	41.91	40.23	13.14	3805	6	283944	438064	0	0.2016	3.6
20/1/1	42.37	40.52	12.42	4025	5	283376	433032	0	0.2108	3.8
50/1/1	40.00	37.94	12.53	3990	2	268864	422168	0	0.207	4.3
5/5/3	38.70	37.06	5.48	9131	896	274960	516096	2 min.	121.0753	5.3
10/5/3	32.98	30.40	5.87	8642	1022	230984	472424	2 min.	121.2158	6.8
20/5/3	37.97	36.34	5.21	9721	836	283760	514104	2 min.	121.1235	19.7
50/5/3	35.46	32.81	5.47	9269	885	238376	478216	2 min. 1 sec.	121.0869	69.3
5/10/6	32.24	28.97	2.93	17359	1857	219896	588280	5 min. 2 sec.	325.505	15.2
10/10/6	37.12	32.94	2.38	21350	1686	269768	625400	5 min. 1 sec.	311.5431	47.6
20/10/6	37.12	35.04	2.60	19567	1013	283224	628792	5 min. 13 sec.	305.2938	253
50/10/6	33.94	31.87	2.56	19808	1082	288608	402664	5 min. 2 sec.	305.0976	1146.8

Legend

* Queue name is ICS Auto Action Time. If no value, the queue file was not created.

N/s – Notifications per second.

NG – No queue growth.

Elapsed Time in Seconds is the time to execute all escalations.

min. – minutes.

sec. – seconds.

Delay in Completion in Seconds is the excess time to complete the execution of the escalations This is measured as the difference between the time the last notification was received by the Service Assurance Manager server and the time the last escalation was completed.

Time to load XML file defines the time it took to load the escalation policies configuration file into the Service Assurance Manager server. This file is in XML format and is loaded into the server using the sm_config command.