....................................................................................................................................................................................................................................

Scaling guidelines for 5620 SAM OSS Clients

OSS client limits

There can be a maximum of 20 5620 SAM OSS-JMS Clients. Greater than 10 5620 SAM

OSS-JMS Clients requires a SAM Server with a minimum of 16 CPU Cores.

The number of 5620 SAM OSS-HTTP Clients supported by a 5620 SAM Server

workstation is 2 times the number of CPU cores with at least 10 and at most 30 clients

supported.

The 3GPP interface can support up to 3 notification clients and 3 action/request clients.

The maximum number of concurrent findToFile operations supported is 5.

5620 SAM OSS Clients using JMS

As of 5620 SAM 9.0R5, OSS Clients using JMS durable connections have a maximum

message rate comparable to non-durable clients.

Network latency between the 5620 SAM Server and a 5620 SAM OSS Client will reduce

the JMS message rate. For durable JMS clients, the Duplicate OK method will allow for a

higher message rate than the Auto Acknowledge method. Refer to the 5620 SAM-O OSS

Interface Developer Guide for more information.

5620 SAM is also able to deliver hundreds of messages per second to a non-durable 5620

SAM OSS client.

Table 6-4

JMS messaging

Durable connection with Auto-acknowledge

(messages/s)

Durable connection with Duplicates-OK

(messages/s)

Notes:

Messaging rates will be lower if using SSL.

6-6

JMS durable messaging rates

Roundtrip latency from the OSS Client to the 5620 SAM Server

0ms

1000

20ms

40ms

690

383

815

418

3HE-09809-AAAG-TQZZA 13.0 R7

OSS client limits

5620 SAM

Issue 1 December 2015

Table of Contents

Scaling Guidelines For 5620 Sam Oss Clients; Oss Client Limits; 5620 Sam Oss Clients Using Jms - Alcatel-Lucent 5620 Planning Manual