IBM Data Server Manager V2.1 - Capacity planning
Note:
The following information is based on the result of IBM® Relational Warehouse
Workload (IRWW) with Unique SQL Rate=1050/s and monitoring profile setting
as this document listed. You might need to adjust the capacity settings per
you own environment if necessary.
Enterprise Edition:(IRWW Workload:Unique SQL Rate=1050/s)
Monitor DB#
CPU(Core)(Intel(R)
Memory
Xeon(R) CPU E5(GB)
2640 0 @ 2.50GHz)
JVM(Max
Heap size)
Disk(GB)
(60
Network(GB)
Days)
1
2
2
-Xmx 512m
2
1
10
2
4
-Xmx 2048m
20
1
50
2
8
-Xmx 6144m
80
1
100
4
16
-Xmx 12288m
160
1
200
8
32
-Xmx 20480m
320
1
250
8
48
-Xmx 32768m
480
1
Base Edition: (IRWW Workload:Unique SQL Rate=1050/s)
CPU(Core)(Intel(R)
Memory
Monitor DB#
Xeon(R) CPU E5(GB)
2640 0 @ 2.50GHz)
JVM(Max
Heap size)
Disk(GB)
Network(GB)
(60Days)
1
1
2
-Xmx 512m
10
1
10
1
4
-Xmx 2048m
10
1
50
1
4
-Xmx 2048m
10
1
100
2
8
-Xmx 4096m
10
1
200
4
12
-Xmx 6144m
10
1
300
6
16
-Xmx 8192m
10
1
400
8
20
-Xmx 10240m
10
1
500
10
32
-Xmx 16384m
10
1
How to use the sizing chart:
1. Locate the chart for the Data Server Manager edition (Enterprise vs Base) you plan to
deploy
-1-
2. Determine how many databases will be monitored/managed by a single Data Server
Manager server in the target environment: small environment (1-50), medium
environment (51-200), large environment (200+)
NOTE: In a DPF environment, Data Server Manager monitors EACH partition as if it is
a single database. So, monitoring a 4-partition DPF database is the same as
monitoring 4 databases.
Legend:
Data Server Manager and Db2 repository server:
•
These products are installed on separate physical machines.
•
The requirements for total CPU, memory and network capacity are the same for
both installations.
•
The Java Heap (Max size) requirement is only applicable to Data Server Manger.
•
The disk requirement is only applicable to the Db2 repository server.
Monitor DB #:
•
The maximum number of monitored databases for which the sizing is suggested.
CPU:
•
The number of cores required by the Data Server Manager and Db2 repository
server.
Memory:
•
The amount of RAM (in GB) required by the Data Server Manager and Db2
repository server.
•
For the Enterprise Edition, the specified amount dose not includes the resource
requirements for the Db2 repository database (assuming it is separated from the
Db2 repository server).
Disk:
•
The amount of disk space required to store product files, work files and monitoring
data.
•
The disk consumption results are obtained from the the Db2 repository server
using the Db2 call get_dbsize_info stored procedure.
JVM parameter:
•
Indicates the maximum heap size value that needs to be set on the Data Server
Manager server.
Network:
•
Indicates the recommended network interface card speed.
-2-
Example:
You want to monitor/manage 200 databases in a production environment using the
Enterprise Edition.
1. Use chart 1
2. To monitor 200 databases you should plan for the following deployment:
Monitor DB#
CPU(Core)(Intel(R)
Memory
Xeon(R) CPU E5(GB)
2640 0 @ 2.50GHz)
JVM(Max
Heap size)
Disk(GB)
(60
Network(GB)
Days)
1
2
2 -Xmx 512m
2
1
10
2
4 -Xmx 2048m
20
1
50
2
8 -Xmx 6144m
80
1
100
4
16 -Xmx 12288m
160
1
200
8
32 -Xmx 20480m
320
1
250
8
48 -Xmx 32768m
480
1
The sizing information is based on the monitoring configuration shown below. Resource
requirements will be higher if data is collected more frequently or retained longer than listed.
Data Server Manager Enterprise Edition reference monitoring configuration for
• In-memory monitoring
-3-
•
Repository persistence
Data Server Manager Base Edition reference monitoring configuration for
• Alerting
-4-