MDB Connectivity Scalability Tests r11 October 25 th 2005

1. MDB Connectivity Scalability Testsr11 October 25th 2005

2. Objectives • The main objective is to determine the Maximum number of MDB connections that can accomplished in a Distributed Deployment. This is particularly important when large number of Distributed State Machines (dsm) are to be deployed • In addition, the test is also geared to determine the limit of maximum number Ingres Sessions based on memory constraints

3. Out-of-Box • Ingres has been configured for 500 Maximum connections • For Local MDB, Ingres Client is configured with InBound=500 and OutBound=500 • For Ingres Client only setup, In Bound and Out Bound limits are configured as 64.

4. MDB Connection Limit MDB Default Medium Size Configuration. The limit will be different for other MDB configuration

5. Ingres Server MDB default Medium Size Configuration NSM r11 Install configures MDB with Medium size settings

6. Ingres Client Only Configuration

7. HA MDB MDB Setup HA Windows Cluster Cluster Node 1 Cluster Node 2 Max Connection Limit = 500 Local MDB exists but connects to Highly Available remote MDB I14YCLUSTER Ingres Client Only Ingres Server I14Y204 I14Y229 In and Out bound Limit = 500 In and Out bound Limit = 64

8. Server Specification MDB Server Ingres Client

9. Test 1 Distributed DSM

10. Objective • The main objective is to determine in a distributed deployment, the number of distributed DSMs (agent technology) with key components installed, can connect to a Central MDB. • The test is performed with out-of-box Ingres Configuration.

11. HA MDB Ingres Client Only I14Y229 MDB Setup HA Windows Cluster Cluster Node 1 Cluster Node 2 Max Connection Limit = 500 I14YCLUSTER In and Out bound Limit = 64

12. MDB – Active Sessions at Start

13. Remote Client - Installed Components

14. Remote Client - Installed Components

15. Ingres Client Session Breakdown • There are 8 permanent sessions from the Ingres Client.

16. Client Connections • If the continuous discovery manager is not installed, this will reduce the number of connections by 2, bringing the permanent connections to 6. • Allow for 4 additional dynamic connections. This will bring the average number of connections to 10. These dynamic connections may be classic 2dmap gui, worldview command line utilities, etc • MDB internally takes up 22 connections. In additional local MDB application takes up 32. The bulk of these are taken up by SevPropCom and Enterprise Management (JMO) • In a typical setup, after 475 connections , out-of-memory condition may be experienced on the local MDB. So the architecture should be designed around 475 max connections

17. Distributed Agent Technology DSMs

18. Conclusion • Without any Ingres configuration customization, approximately 42 Agent Technology DSMs can connect to one MDB. • If more than 42 dsms need to be deployed then federated MDB concept should be reviewed

19. Test 2

20. Objectives • Analyze the impact if the inbound or outbound limit is exhausted • Out-of-box, the Inbound and Outbound limits are set to 64. If this limit is exhausted, it will not be able to connect to the MDB until some connections are released

21. Test 2 • Connect to Highly Available remote MDB from Ingres Client setup • Setup a Loop to connect remote CORE (mdb) until it fails to connect • Review Ingres Connections • Out-of-box Inbound an Out bound limit set to 64.It cannot exceed this limit

22. HA MDB Ingres Client Only I14Y229 MDB Setup HA Windows Cluster Cluster Node 1 Cluster Node 2 Max Connection Limit = 500 I14YCLUSTER In and Out bound Limit = 64

23. MDB – Active Sessions at Start

24. Generate Additional Connections from Ingres Client Setup Fails to connect after 56 connections as expected.

25. Aws_dsm fails with rc=28

26. Ingres Sessions Review on Local MDB Confirms failure due to In/Out Bound Limit

27. Connection breakdown by Applications This is not a comprehensive list. Shows breakdown of Ingres Sessions for key applications running on the HA Server connecting to the local HA MDB

28. Conclusion • If the Inbound or Outbound limit is exhausted, the wv connection will fail with return code 28 • aws_dsm may loose a connection but will reconnect when MDB connection is available

29. Test 3 Out-of-Memory Test

30. Objectives • The main objective is to exhaust the Ingres Connections until out-of-memory condition is experienced. Then ascertain the maximum number of active connections.

31. Fails to Connect after 415 additional connections

32. Out-of-Memory • Attempt to launch SQL from local MDB server fails due to out-of-memory condition

33. Ingres Sessions Review on Local MDB • Stop awservices to release 4 sessions. • This shows Ingres Sessions after stopping awservices Confirms failure due to out-of-memory

34. Conclusions • After connection of approximately 475 sessions, no more connections will be possible to the MDB due to out of memory condition.

35. Test 4 DSM Session Breakdown

36. Test 4 • The main objective is to provide breakdown by process of DSM mdb sessions. • The test was performed with not much activity except one DSMExplorer was launched.

37. Domain Management Component Database Communication

38. DSM – MDB Connection Breakdown

39. DSM • In summary, DSM will take approx 18 connection when Asset Domain Manager and Software delivery. • This is connecting a remote MDB