Transcript MDB Connectivity Scalability for r11 NSM

MDB Connectivity
Scalability Tests
r11
October 25th 2005
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
2
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
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.
3
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
MDB Connection Limit
MDB Default Medium Size
Configuration. The limit will
be different for other MDB
configuration
4
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Ingres Server
NSM r11 Install
configures MDB with
Medium size settings
5
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
MDB default
Medium Size
Configuration
Ingres Client Only Configuration
6
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
MDB Setup
HA Windows Cluster
Cluster Node 1
Local MDB
exists but
connects to
Highly
Available
remote MDB
HA
MDB
Ingres Server
Cluster Node 2
Max Connection Limit
= 500
I14YCLUSTER
Ingres Client
Only
I14Y204
In and Out bound
Limit = 500
8
I14Y229
In and Out bound
Limit = 64
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Server Specification
MDB Server
Ingres Client
9
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Test 1
- Distributed DSM
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
MDB Setup
HA Windows Cluster
Cluster Node 1
HA
MDB
Cluster Node 2
I14YCLUSTER
Ingres Client
Only
I14Y229
In and Out bound
Limit = 64
12
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Max Connection Limit
= 500
MDB – Active Sessions at Start
Client Host
13
No of Active Sessions
Internal
22
Ingres Client
8
Local server
32
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Remote Client - Installed Components
14
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Remote Client - Installed Components
15
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Ingres Client Session Breakdown
- There are 8 permanent sessions from the Ingres Client.
16
Application
Number of
Sessions
aws_wvgate
2
Continues Discovery Manager
2
aws_dsm
2
ca-notify
1
Worldview Agent
1
Total Sessions at Start
8
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Distributed Agent Technology DSMs
Maximum number of Active Connections
475
Permanent Connections
Local MDB
32
Internal
22
Number of Connection Available for Remote Clients
421
Number of Permanent Connections
aws_wvgate
2
aws_dsm
2
Worlview Agent
1
CA-Notify
1
Additional dynamic Connections
4
Total likely Connections per DSM Setup
10
Max number of DSM per MDB
18
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
42
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Test 2
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
MDB Setup
HA Windows Cluster
Cluster Node 1
HA
MDB
Cluster Node 2
I14YCLUSTER
Ingres Client
Only
I14Y229
In and Out bound
Limit = 64
23
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Max Connection Limit
= 500
MDB – Active Sessions at Start
Client Host
24
No of Active Sessions
Internal
22
Ingres Client
8
Local server
32
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Generate Additional Connections from
Ingres Client Setup
Fails to connect after 56
connections as expected.
25
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Aws_dsm fails with rc=28
26
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Ingres Sessions Review on Local MDB
Confirms failure
due to In/Out
Bound Limit
27
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Connection breakdown by Applications
Application
Average Number of Sessions
JMO (WLM)
8
SevProp
5
StartBPV
2
rmi_Server
4
setdsmname
2
Component Security
3
aws_dsm
2
aws_wvgate
2
wvobjectcell
1
Ingres (Internal)
22
wv Tools
objbrows
1
catng2d
1
managobj
1
ca-notify
1
Total
54
This is not a comprehensive list. Shows breakdown of
Ingres Sessions for key applications running on the HA
28
Server connecting to the local HA MDB
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Test 3
- Out-of-Memory Test
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Fails to Connect after 415 additional
connections
32
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Out-of-Memory
- Attempt to launch SQL from local MDB server fails due to
out-of-memory condition
33
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Ingres Sessions Review on Local MDB
- Stop awservices to release 4 sessions.
- This shows Ingres Sessions after stopping awservices
Confirms failure
due to out-ofmemory
34
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Conclusions
- After connection of approximately 475 sessions, no more
connections will be possible to the MDB due to out of
memory condition.
35
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Test 4
- DSM Session Breakdown
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
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Domain Management Component
MDB
DB
DB
Database
Communication
Domain Manager
DB
Engine
DB
Scalability Server
DSM Explorer
Reporter
38
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
DSM – MDB Connection Breakdown
MDB User
Group
Process
Count
ca_itrm
ca_itrm_group
amobjectmanager.exe
3
ca_itrm
regadmin
amobjectmanager.exe
1
ca_itrm
ca_itrm_group
cmEngine.exe
3
ca_itrm
ca_itrm_group
egc30n.exe
3
ca_itrm
ca_itrm_group
sd_taskm.exe
3
ca_itrm
ca_itrm_group
cmobjectmanager.exe
1
ca_itrm
ca_itrm_group
dmdeploy.exe
1
ca_itrm
ca_itrm_group
sd_apisrv.exe
1
ca_itrm
ca_itrm_group
sd_dialog_m.exe
1
ca_itrm
ca_itrm_group
tngdtdtos.exe
1
Total
39
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
18
DSM
- In summary, DSM will take approx 18 connection when
Asset Domain Manager and Software delivery.
- This is connecting a remote MDB
40
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.