1. TrueSight Capacity Optimization @Sanofi
December 13, 2018
Architecture Review
Mike West

2. Current Sizing Input - Total Load: 48Mrows/day
entity type
# entities
metric resolution [sec]
number metrics
Virtual Machine - VMware
21306
3600
196
Database Instance
3609
3576 33
Datastore
1468 13
Virtual Machine - HP Integrity
1192
487
Virtual Host - VMware
709 92
Storage Filer
618
1140 10
Generic
357
300
440
Storage Pool
296 14
Virtual Host - HP Integrity
161
732
Virtual Cluster - VMware
113 57
Datastore Cluster - VMware
100 4
entity type
# entities
metric resolution [sec]
number metrics
Hadoop Node 53
47748 37
Storage System 45
900
824
Hadoop Resource Pool 41
3600 61
Virtual Machine - AIX Shared Processor LPAR 35
385
Virtual Machine - Solaris Zone 31 16
Storage Share 24
86400 78
Virtual Application - VMware vApp 23 11
Datacenter 20 4
Network - Switch
321
Virtual Node - VMware 15
110
Others 69
Various
236

3. automatic data summarization
Data Retention
Default
values
Customer
values
Data Warehouse
Engine
monthly
Based on the Measure TS, data is maintained days 720 days
daily
Based on the Measure TS, data is maintained days 240 days
automatic data summarization
hourly
Based on the Measure TS, data is maintained days 120 days
CDB
detail
Based on the Measure TS, data is maintained days 120 days
Stage
Based on the Insertion TS, data is maintained days 5 days

4. TrueSight Capacity Optimization 10.7.01
Sizing

6. Server Requirements – 10.7.01 Component # Systems Processor Memory
Storage | Software
AS – Primary Server
(+Data Hub +Web)
OS: Linux 1
4 processors
16 GB
20 GB GB repository
TSPS
OS: Linux/Windows
200 GB
ASSO
2 processors
8 GB
100 GB
ETL Engine 4
Gateway Server – Automation
393 GB GWS server – assumes 80% compression for UDR data
150 IOPS
Database Server
OS: Any supported by DB technology
8 processors
12 GB Instance Memory
Tablespace, excluding ARCHIVE/REDO
Total: 2,475 GB
Performance: IOPS
DB options:
Oracle EE (partitioning enabled), ASM (virtualize storage), AMM or ASMM (manage instance memory)

7. DB Tablespace Allocation – 10.7.01
For better performance, BMC recommends allocating the 2 data tablespaces (BCO and BCO_DATA) on a different storage device than the 2 index tablespaces (BCO_IDX, BCO_DATA_IDX).
The default schema owner user is BCO_OWN. This user must have permissions on all the tablespaces and also on a temporary tablespace. The schema uses global temporary tables that can reach considerable size.
BMC also recommends that auto-extend be turned ON for all tablespaces in order to allow each to grow when space is required. The following table provides the table dimension and the recommended extent size.
Tablespace
Storage location
Dimension
Extent size
BCO A
9 GB
128 KB
BCO_IDX B
BCO_DATA
1,495 GB
8 MB or 16 MB 
BCO_DATA_IDX
961 GB

8. DB Tablespace Allocation – 10.7.01
E.1 Estimated DWH size
REGIME
MILESTONE 1
MILESTONE 2
MILESTONE 3
120
months 6 12 24
TABLESPACES MB GB
CPIT
9,282
9.06
CPIT_IDX
CPIT_DATA
1,531,168
1,495.28
1,175,264
1,147.72
1,301,968
1,271.45
CPIT_DATA_IDX
984,304
961.23
761,968
744.11
841,056
821.34
BUFFER & ER TABLES (with idx) -
TOTAL
2,534,036
2,475
1,955,796
1,910
2,161,588
2,111

9. DB Auxiliary tablespaces requirements – 10.7.01
Size
Notes
Temporary
> 3 GB -
UNDO
REDO logs
> 4 GB
Allocate enough archive space to accommodate the REDO logs between backup intervals. For example, if backup is taken every six hours, then the archive space will need to be > 79 GB.

10. TrueSight Capacity Optimization 11.3.01
Sizing

11. TrueSight Capacity Optimization 11.3.01 Reference Architecture
Browser
analysis, viewing
analysis, viewing
access capacity agent data
load data (optional - remote)
Application
Server
Admin
Workspace
Report
Virtual Planner
Reservations
Chargeback
Automation
Managed Systems
w/ Capacity Agents
Gateway Server
(Linux | Windows)
ETL Engine
Server
Database
Server
capacity agent data
transfer VIS
load data
access data
Gateway Service
access data
access UDR
extract data
user authentication
Presentation
Server
Cloud Cost Control
Investigate
Capacity Views
Analyze
Gateway Server
(Windows)
Third Party
Data Sources
RSSO
Server
New product / capabilities
Supported capabilities
Predict
TLS 1.2 support where possible
No TLS 1.2 support
user authentication

12. Server Requirements – 11.3.01 Component # Systems Processor Memory
Storage | Software
AS – Primary Server
(+Data Hub +Web)
OS: Linux 1
4 processors
16 GB
20 GB GB repository
TSPS
OS: Linux/Windows
200 GB
RSSO
2 processors
8 GB
100 GB
ETL Engine 4
Gateway Server – Automation
393 GB GWS server – assumes 80% compression for UDR data
150 IOPS
Database Server
OS: Any supported by DB technology
8 processors
12 GB Instance Memory
Tablespace, excluding ARCHIVE/REDO
Total: 2,475 GB
Performance: 2,382 IOPS
DB options:
Oracle EE (partitioning enabled), ASM (virtualize storage), AMM or ASMM (manage instance memory)

13. DB Tablespace Allocation – 11.3.01
For better performance, BMC recommends allocating the 2 data tablespaces (BCO and BCO_DATA) on a different storage device than the 2 index tablespaces (BCO_IDX, BCO_DATA_IDX).
The default schema owner user is BCO_OWN. This user must have permissions on all the tablespaces and also on a temporary tablespace. The schema uses global temporary tables that can reach considerable size.
BMC also recommends that auto-extend be turned ON for all tablespaces in order to allow each to grow when space is required. The following table provides the table dimension and the recommended extent size.
Tablespace
Storage location
Dimension
Extent size
BCO A
9 GB
128 KB
BCO_IDX B
BCO_DATA
1,495 GB
8 MB or 16 MB 
BCO_DATA_IDX
961 GB

14. DB Tablespace Allocation – 11.3.01
E.1 Estimated DWH size
REGIME
MILESTONE 1
MILESTONE 2
MILESTONE 3
120
months 6 12 24
TABLESPACES MB GB
CPIT
9,282
9.06
CPIT_IDX
CPIT_DATA
1,531,168
1,495.28
1,175,264
1,147.72
1,301,968
1,271.45
CPIT_DATA_IDX
984,304
961.23
761,968
744.11
841,056
821.34
BUFFER & ER TABLES (with idx) -
TOTAL
2,534,036
2,475
1,955,796
1,910
2,161,588
2,111

15. DB Auxiliary tablespaces requirements – 11.3.01
Size
Notes
Temporary
> 3 GB -
UNDO
REDO logs
> 4 GB
Allocate enough archive space to accommodate the REDO logs between backup intervals. For example, if backup is taken every six hours, then the archive space will need to be > 84 GB.

16. — Bring IT to Life.™