This document is intended to provide a guideline in helping size CA PPM for your implementation based on the CA PPM 15.x Performance White Paper. This document in no way guarantees performance, but rather a baseline to start from. Based on this initial recommendation, customers are required to develop their own deployment architecture specifications/diagrams. Other hardware architectures may support less/more active users than what is currently detailed. The customer is ultimately responsible for validating recommendation. This could result in the increase/decrease of required resources to meet implementation requirements. Moving forward, x86 64bit architectures will be the primary hardware architecture recommended.
Additional discussions can be setup to finalize the overall architecture with a CA PPM Presales, CA Services Architect or qualified CA Partner. The final architecture should be reviewed prior to applying any deployment architecture for your CA PPM implementation.
Please refer to the latest CA PPM Product Architecture stack contained within the Compatibilities section of the latest Release Notes at https://wiki.ca.com for details on current supported software architectures.
Guidelines
Database Tier ‐ PPMx86 64bit OS – DBMS:2 x 2.6 GHz Xeon Cores4 GB Oracle Max Memory5 GB Storage per yrRAID 0 + 1 or 10
Application Tierx86 64bit OS – Tomcat:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 6 GB RAM30 GB Disk Space per nodeRAID 1 or 5
Reporting Tierx86 64bit OS – Tomcat: 1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 4 GB RAM40 GB Disk SpaceRAID 0 + 1 or 10
CSS Content Switch orLoad Balancer
Private LAN
VLAN
High Speed/Low Latency LANMulticast Enabled
CA PPM
Notes: The following deployment architecture will support up to 75 active users based on user types and functionality implemented. As additional users are added or functionality implemented, additional application servers can be added to the deployment architecture to distribute the CA PPM application and background services. The number of cores per VM will vary based on implementation size/scope.
The following recommendations are just that, recommendations. This recommendation should be used in developing your own deployment architecture. Additional discussions should be setup to review and finalize the production deployment architecture.
APPLICATION TIERNAS Storage
Reporting Tier
JasperSoft Reports
*support for 100 users (20 active users – 20% of Total Users)30% ‐ Managers 70% ‐ Team Members
Requirements Planning Project Manager Resource Manager Project Portfolio Manager IT Portfolio Manager Process Manager Demand Manager Project Financial Manager IT Financial Manager CA PPM Studio Schedule Connect CA PPM Time
CA PPM Functional Modules
High Speed/Low Latency LAN
DATABASE TIERSAN Storage
FiberDB Node
Oracle Or
MS SQL Server
* CA Productivity AcceleratorWindows 2008 64bit OS – Web Server:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 4 GB RAM30 GB Disk Space per nodeRAID 1 or 5
* CA Productivity Accelerator(CAPA): Option if purchased with CA PPM. Sizing is based on multi‐user installation of CAPA. If the CAPA Knowledge Center is deployed, then double the hardware requirements.
CA PPM r15.x – 100 Users
Database Tier ‐ DWHx86 64bit OS – DBMS:2 x 2.6 GHz Xeon Cores2 GB Oracle Max MemoryRAID 0 + 1 or 10
Application Tier JVM
Java Arg = ‐Xmx2048m
Background JVM
Java Arg = ‐Xmx1024m
CSA JVM
Java Arg = ‐Xmx1024m
JVM Configuration Setup
The following are base memory configuration for the following CA PPM application components. While these components are separated below, a combination may be contained within a single VM based on requirements.
Each CA PPM Application instance should handle 75 active users based on user types and functionality implemented for each sample.MaxThreads for each Tomcat application JVM should =200. JasperSoft Install should support 15 Active Users (15% of total active PPM users)
JasperSoft User Type Users Percentage of TotalHeavy users 2 15%Active Users 7 45%Moderate Users 4 25%Light Users 2 15%
Total 15 100%
Reporting – VM 1
JasperSoft Server
Web Browser
OWB or MSP
Web Browser
App Tier ‐ VM 1
Network Switch
App Node 1A-Xmx2048m
BG Node 1A-Xmx1024m
CSA Node 1A-Xmx1024m
HTTP or HTTPS Load BalancersHTTP or HTTPS Direct
Production Data Direct JDBCProduction JasperSoft JDBC
JasperSoft Web ServiceMulticast
NOTE: Multicast is required to be active at the router layer so that the CA PPM cluster services correctly communicate. On router/switches, make sure IGMP snooping is enabled and that broadcast suppression is not in use.
CAPA ‐ VM
CAPA Node 1A4GB
* CA Productivity Accelerator option if purchased
CA PPM r15.x Logical – 100 Users
Report Node 1A-Xmx2048m
Transactional Database
PPM Schema DWH Schema
DataWarehouse Database
DWH Load
NOTE: While the DWH schema is depicted on a separate database server, it could reside within the same database instance under this capacity.
Database Tier ‐ PPMx86 64bit OS – DBMS:4 x 2.6 GHz Xeon Cores6 GB Oracle Max Memory10 GB Storage per yrRAID 0 + 1 or 10
Application Tierx86 64bit OS – Tomcat:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 8 GB RAM30 GB Disk Space per nodeRAID 1 or 5
Reporting Tierx86 64bit OS – Tomcat:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 6 GB RAM40 GB Disk Space per nodeRAID 0 + 1 or 10
CSS Content Switch orLoad Balancer
Private LAN
VLAN
High Speed/Low Latency LANMulticast Enabled
CA PPM
Notes: The following deployment architecture will support up to 175 active users based on user types and functionality implemented. As additional users are added or functionality implemented, additional application servers can be added to the deployment architecture to distribute the CA PPM application and background services. The number of cores per VM will vary based on implementation size/scope.
The following recommendations are just that, recommendations. This recommendation should be used in developing your own deployment architecture. Additional discussions should be setup to review and finalize the production deployment architecture.
APPLICATION TIERNAS Storage
Reporting Tier
JasperSoft Reports
*support for 500 users (100 active users – 20% of Total Users)30% ‐ Managers 70% ‐ Team Members
Requirements Planning Project Manager Resource Manager Project Portfolio Manager IT Portfolio Manager Process Manager Demand Manager Project Financial Manager IT Financial Manager CA PPM Studio Schedule Connect CA PPM Time
CA PPM Functional Modules
High Speed/Low Latency LAN
DATABASE TIERSAN Storage
FiberDB Node
Oracle Or
MS SQL Server
* CA Productivity AcceleratorWindows 2008 64bit OS – Web Server:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 4 GB RAM30 GB Disk Space per nodeRAID 1 or 5
* CA Productivity Accelerator(CAPA): Option if purchased with CA PPM. Sizing is based on multi‐user installation of CAPA. If the CAPA Knowledge Center is deployed, then double the hardware requirements.
CA PPM r15.x – 500 Users
Database Tier ‐ DWHx86 64bit OS – DBMS:2 x 2.6 GHz Xeon Cores4 GB Oracle Max MemoryRAID 0 + 1 or 10
Application Tier JVM
Java Arg = ‐Xmx3072m
Background JVM
Java Arg = ‐Xmx2048m
CSA JVM
Java Arg = ‐Xmx1024m
JVM Configuration Setup
The following are base memory configuration for the following CA PPM application components. While these components are separated below, a combination may be contained within a single VM based on requirements.
Each CA PPM Application instance should handle 175 active users based on user types and functionality implemented for each sample.MaxThreads for each Tomcat application JVM should =300. JasperSoft Install should support 30 Active Users (15% of total active PPM users)
Jasper User Type Users Percentage of TotalHeavy users 4 15%Active Users 14 45%Moderate Users 8 25%Light Users 4 15%
Total 30 100%
CA PPM r15.x JVM – 500 Users
Web Browser
OWB or MSP
Web Browser
App Tier ‐ VM 1
App Node 1A-Xmx3072m
BG Node 1A-Xmx2048m
CSA Node 1A-Xmx1024m
Network Switch
NOTE: Multicast is required to be active at the router layer so that the Clarity cluster services correctly communicate. On router/switches, make sure IGMP snooping is enabled and that broadcast suppression is not in use.
CAPA ‐ VM
CAPA Node 1A4GB
* CA Productivity Accelerator option if purchased
CA PPM r15.x Logical – 500 Users
Reporting – VM 1
JasperSoft Server
Report Node 1A-Xmx3072m
Transactional Database
PPM Schema DWH Schema
DataWarehouse Database
DWH LoadHTTP or HTTPS Load BalancersHTTP or HTTPS Direct
Production Data Direct JDBCProduction JasperSoft JDBC
JasperSoft Web ServiceMulticast
NOTE: While the DWH schema is depicted on a separate database server, it could reside within the same database instance under this capacity.
Database Tier ‐ PPMx86 64bit OS – DBMS:6 x 2.6 GHz Xeon Cores12 GB Oracle Max Memory18 GB Storage per yrRAID 0 + 1 or 10
Application Tierx86 64bit OS – Tomcat:2 – Virtual Machines2 Cores @ 2.6 GHz Xeon 8 GB RAM30 GB Disk Space per nodeRAID 1 or 5
Reporting Tierx86 64bit OS – Tomcat:1 – Virtual Machines2 Cores @ 2.6 GHz Xeon 6 GB RAM40 GB Disk Space per nodeRAID 0 + 1 or 10
CSS Content Switch orLoad Balancer
Private LAN
VLAN
High Speed/Low Latency LANMulticast Enabled
ESX Server
UNC Mount
CA PPM
Notes: The following deployment architecture will support up to 350 active users based on user types and functionality implemented. As additional users are added or functionality implemented, additional application servers can be added to the deployment architecture to distribute the CA PPM application and background services. The number of cores per VM will vary based on implementation size/scope.
The following recommendations are just that, recommendations. This recommendation should be used in developing your own deployment architecture. Additional discussions should be setup to review and finalize the production deployment architecture.
ESX Server
UNC Mount
ESX Server
APPLICATION TIERNAS Storage
Reporting Tier
JasperSoft Reports
*support for 1,000 users (200 active users – 20% of Total Users)30% ‐ Managers 70% ‐ Team Members
Requirements Planning Project Manager Resource Manager Project Portfolio Manager IT Portfolio Manager Process Manager Demand Manager Project Financial Manager IT Financial Manager CA PPM Studio Schedule Connect CA PPM Time
CA PPM Functional Modules
Background Tierx86 64bit OS – Tomcat:2 – JVMsIncorporated within App Tier VMs
XOG Tierx86 64bit OS – Tomcat:1 – Virtual Machines2 Cores @ 2.6 GHz Xeon 6 GB RAM30 GB Disk Space per nodeRAID 1 or 5
High Speed/Low Latency LAN
DATABASE TIERSAN Storage
FiberDB Node
Oracle Or
MS SQL Server
* CA Productivity AcceleratorWindows 2008 64bit OS – Web Server:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 4 GB RAM30 GB Disk Space per nodeRAID 1 or 5
* CA Productivity Accelerator(CAPA): Option if purchased with CA PPM. Sizing is based on multi‐user installation of CAPA. If the CAPA Knowledge Center is deployed, then double the hardware requirements.
CA PPM r15.x – 1k Users
Database Tier ‐ DWHx86 64bit OS – DBMS:4 x 2.6 GHz Xeon Cores6 GB Oracle Max MemoryRAID 0 + 1 or 10
Clarity v12.1 Logical VM Breakout
Application Tier JVM
Java Arg = ‐Xmx3072m
XOG Tier JVM
Java Arg = ‐Xmx2048m
Background JVM
Java Arg = ‐Xmx2048m
CSA JVM
Java Arg = ‐Xmx1024m
JVM Configuration Setup
The following are base memory configuration for the following CA PPM application components. While these components are separated below, a combination may be contained within a single VM based on requirements.
Each CA PPM Application instance should handle 175 active users based on user types and functionality implemented for each sample.MaxThreads for each Tomcat application JVM should =300. MaxThreads for each XOG Tomcat application JVM should = 300JasperSoft Install should support 60 Active Users (15% of total active PPM users) or 150 reports in an hour at peak usage.
Jasper User Type Users Percentage of TotalHeavy users 9 15%Active Users 27 45%Moderate Users 15 25%Light Users 9 15%
Total 60 100%
Web Browser
OWB or MSP
Web Browser
NOTE: This Logical example outlines how the CA PPM services should be scaled based on the appropriate hardware in place. The number of services and servers required will vary based on your implementation. This also provides some insight on connectivity between the services within the CA PPM cluster.
Recommend routing return HTTP traffic through an independent direct switch/router rather than through the load balancers to help reduce network latency.
CSS Load Balancer
App Tier ‐ VM 1 App Tier ‐ VM 2 App Tier ‐ VM 3
CSA Node 1A-Xmx1024m
App Node 1A-Xmx3072m
Network Switch
App Node 2A-Xmx3072m
BG Node 2A-Xmx2048m
XOG Node 3A-Xmx2048m
BG Node 3A-Xmx2048m
NOTE: Multicast is required to be active at the router layer so that the CA PPM cluster services correctly communicate. On router/switches, make sure IGMP snooping is enabled and that broadcast suppression is not in use.
CAPA ‐ VM
CAPA Node 1A4GB
* CA Productivity Accelerator option if purchased
CA PPM r15.x Logical – 1k Users
Reporting – VM 1
JasperSoft Server
Report Node 1A-Xmx4096m
HTTP or HTTPS Load BalancersHTTP or HTTPS Direct
Production Data Direct JDBCProduction JasperSoft JDBC
JasperSoft Web ServiceMulticast
Transactional Database
PPM Schema DWH Schema
DataWarehouse Database
DWH Load
Database Tier ‐ PPMx86 64bit OS – DBMS:8 x 2.6 GHz Xeon Cores16 GB Oracle Max Memory45 GB Storage per yrRAID 0 + 1 or 10
Application Tierx86 64bit OS – Tomcat:2 – Virtual Machines4 Cores @ 2.6 GHz Xeon 10 GB RAM30 GB Disk Space per nodeRAID 1 or 5
Reporting Tierx86 64bit OS:2 – Virtual Machines2 Cores @ 2.6 GHz Xeon 8 GB RAM40 GB Disk Space per nodeRAID 0 + 1 or 10
CSS Content Switch orLoad Balancer
LAN
VLAN
High Speed/Low Latency LANMulticast Enabled
ESX Server
UNC Mount
CA PPM
Notes: The following deployment architecture will support up to 550 active users based on user types and functionality implemented. As additional users are added or functionality implemented, additional application servers can be added to the deployment architecture to distribute the CA PPM application and background services. The number of cores per VM will vary based on implementation size/scope.
The following recommendations are just that, recommendations. This recommendation should be used in developing your own deployment architecture. Additional discussions should be setup to review and finalize the production deployment architecture.
ESX Server
UNC Mount
ESX Server
APPLICATION TIERNAS Storage
CA PPM r15.x – 2.5k Users
Reporting Tier
JasperSoft Reports
*support for 2,500 users (500 active users – 20% of Total Users)30% ‐ Unrestricted 70% ‐ Restricted
Requirements Planning Project Manager Resource Manager Project Portfolio Manager IT Portfolio Manager Process Manager Demand Manager Project Financial Manager IT Financial Manager CA PPM Studio Schedule Connect CA PPM Time
CA PPM Functional Modules
Background Service Tierx86 64bit OS – Tomcat:2 – JVMsIncorporated within App & Xog Tier VMs
XOG Tierx86 64bit OS – Tomcat:1 – Virtual Machines2 Cores @ 2.6 GHz Xeon 8 GB RAM30 GB Disk Space per nodeRAID 1 or 5
High Speed/Low Latency LAN
DATABASE TIER SAN
FiberDWH DB Node
Oracle Or
MS SQL Server
* CA Productivity AcceleratorWindows 2008 64bit OS – Web Server:1 – Virtual Machine2 Cores @ 2.6 GHz Xeon 4 GB RAM30 GB Disk Space per nodeRAID 1 or 5
* CA Productivity Accelerator(CAPA): Option if purchased with CA PPM. Sizing is based on multi‐user installation of CAPA. If the CAPA Knowledge Center is deployed, then double the hardware requirements.
Fiber
PPM DB Node
Database Tier ‐ DWHx86 64bit OS – DBMS:4 x 2.6 GHz Xeon Cores6 GB Oracle Max MemoryRAID 0 + 1 or 10
CA PPM v12.1 Logical VM Breakout
Application Tier JVM
Java Arg = ‐Xmx4096m
XOG Tier JVM
Java Arg = ‐Xmx3072m
Background JVM
Java Arg = ‐Xmx3072m
CSA JVM
Java Arg = ‐Xmx1024m
JVM Configuration Setup
The following are base memory configuration for the following CA PPM application components. While these components are separated below, a combination may be contained within a single VM based on requirements.
Each CA PPM Application instance should handle 275 active users based on user types and functionality implemented for each sample.MaxThreads for each Tomcat application JVM should =350. MaxThreads for each XOG Tomcat application JVM should = 350JasperSoft Install should support 150 Active Users (30% of total active PPM users) or 200 reports in an hour at peak usage.
Jasper User Type Users Percentage of TotalHeavy users 23 15%Active Users 67 45%Moderate Users 37 25%Light Users 23 15%
Total 150 100%
Reporting JVM 1
Java Arg = ‐Xmx4096m
Report Server
Reporting JVM 2
Java Arg = ‐Xmx4096m
Report Server
Web Browser
OWB or MSP
Web Browser
Transactional Database
NOTE: This Logical example outlines how the CA PPM services should be scaled based on the appropriate hardware in place. The number of services and servers required will vary based on your implementation. This also provides some insight on connectivity between the services within the CA PPM cluster.
Recommend routing return HTTP traffic through an independent direct switch/router rather than through the load balancers to help reduce network latency.
App Tier ‐ VM 1 App Tier ‐ VM 2 App Tier ‐ VM 3
Reporting – VM 1
Reporting – VM 2
CA PPM r15.x Logical – 2.5k Users
CSA Node 1A-Xmx1024m
App Node 1A-Xmx4096m
PPM Schema
CSS Load Balancer
Network Switch
BG Node 2A-Xmx3072m
App Node 2A-Xmx4096m
BG Node 3A-Xmx3072m
HTTP or HTTPS Load BalancersHTTP or HTTPS DirectProduction Data Direct JDBCProduction Jasper JDBCJasperSoft Web ServiceMulticast
XOG Node 3A-Xmx3072m
NOTE: Multicast is required to be active at the router layer so that the CA PPM cluster services correctly communicate. On router/switches, make sure IGMP snooping is enabled and that broadcast suppression is not in use.
CAPA ‐ VM
CAPA Node 1A4GB
* CA Productivity Accelerator option if purchased
DWH Schema
DataWarehouse Database
DWH Load
JasperSoft Cluster
Report Node 1A-Xmx4096m
Report Node 2A-Xmx4096m
Database Tier ‐ PPMx86 64bit OS – DBMS:12 x 2.6 GHz Xeon Cores32 GB Oracle Max Memory90 GB Storage per yrRAID 0 + 1 or 10
Application Tierx86 64bit OS – Tomcat:3 – Virtual Machines6 Cores @ 2.6 GHz Xeon 12 GB RAM30 GB Disk Space per nodeRAID 1 or 5
Reporting Tierx86 64bit OS:3 – Virtual Machines2 Cores @ 2.6 GHz Xeon 8 GB RAM40 GB Disk Space per nodeRAID 0 + 1 or 10
CSS Content Switch orLoad Balancer
LAN
VLAN
High Speed/Low Latency LANMulticast Enabled
ESX Server
UNC Mount
CA PPM
Notes: The following deployment architecture will support up to 1,200 active users based on user types and functionality implemented. As additional users are added or functionality implemented, additional application servers can be added to the deployment architecture to distribute the CA PPM application and background services. The number of cores per VM will vary based on implementation size/scope.
The following recommendations are just that, recommendations. This recommendation should be used in developing your own deployment architecture. Additional discussions should be setup to review and finalize the production deployment architecture.
ESX Server
UNC Mount
ESX Server
APPLICATION TIERNAS Storage
CA PPM r15.x – 5K Users
Reporting Tier
JasperSoft Reports
*support for 5,000 users (1,000 active users – 20% of Total Users)30% ‐ Unrestricted 70% ‐ Restricted
Requirements Planning Project Manager Resource Manager Project Portfolio Manager IT Portfolio Manager Process Manager Demand Manager Project Financial Manager IT Financial Manager CA PPM Studio Schedule Connect CA PPM Time
CA PPM Functional Modules
Background Service Tierx86 64bit OS – Tomcat:2 – JVMsIncorporated within App & Xog Tier VMs
XOG Tierx86 64bit OS – Tomcat:1 – Virtual Machines2 Cores @ 2.6 GHz Xeon 8 GB RAM30 GB Disk Space per nodeRAID 1 or 5
High Speed/Low Latency LAN
DATABASE TIER SAN
FiberDWH DB Node
Oracle Or
MS SQL Server
* CA Productivity AcceleratorWindows 2008 64bit OS – Web Server:1 – Virtual Machine4 Cores @ 2.6 GHz Xeon 6 GB RAM30 GB Disk Space per nodeRAID 1 or 5
* CA Productivity Accelerator(CAPA): Option if purchased with CA PPM. Sizing is based on multi‐user installation of CAPA. If the CAPA Knowledge Center is deployed, then double the hardware requirements.
Fiber
PPM DB Node
Database Tier ‐ DWHx86 64bit OS – DBMS:6 x 2.6 GHz Xeon Cores10 GB Oracle Max MemoryRAID 0 + 1 or 10
CA PPM v12.1 Logical VM Breakout
Application Tier JVM
Java Arg = ‐Xmx6144m
XOG Tier JVM
Java Arg = ‐Xmx4096m
Background JVM
Java Arg = ‐Xmx4096m
CSA JVM
Java Arg = ‐Xmx1024m
JVM Configuration Setup
The following are base memory configuration for the following CA PPM application components. While these components are separated below, a combination may be contained within a single VM based on requirements.
Each CA PPM Application instance should handle 400 active users based on user types and functionality implemented for each sample.MaxThreads for each Tomcat application JVM should =450. MaxThreads for each XOG Tomcat application JVM should = 350JasperSoft Install should support 300 Active Users (30% of total active PPM users) or 400 reports in an hour at peak usage.
Jasper User Type Users Percentage of TotalHeavy users 44 15%Active Users 136 45%Moderate Users 76 25%Light Users 44 15%
Total 300 100%
Reporting JVM 1
Java Arg = ‐Xmx6144m
Report Server
Reporting JVM 2
Java Arg = ‐Xmx6144m
Report Server
Reporting JVM 3
Java Arg = ‐Xmx6144m
Scheduling Server
Web Browser
Transactional Database
NOTE: This Logical example outlines how the CA PPM services should be scaled based on the appropriate hardware in place. The number of services and servers required will vary based on your implementation. This also provides some insight on connectivity between the services within the CA PPM cluster.
Recommend routing return HTTP traffic through an independent direct switch/router rather than through the load balancers to help reduce network latency.
App Tier ‐ VM 1 App Tier ‐ VM 2 App Tier ‐ VM 4
Reporting – VM 1
Reporting – VM 2
CA PPM r15.x Logical – 5K Users
CSA Node 1A-Xmx1024m
App Node 1A-Xmx6144m
PPM Schema
CSS Load Balancer
Network Switch
App Node 2A-Xmx6144m
HTTP or HTTPS Load BalancersHTTP or HTTPS DirectProduction Data Direct JDBCProduction Jasper JDBCJasperSoft Web ServiceMulticast
NOTE: Multicast is required to be active at the router layer so that the CA PPM cluster services correctly communicate. On router/switches, make sure IGMP snooping is enabled and that broadcast suppression is not in use.
CAPA ‐ VM
CAPA Node 1A6GB
* CA Productivity Accelerator option if purchased
DWH Schema
DataWarehouse Database
DWH Load
JasperSoft Cluster
App Tier ‐ VM 3
Reporting – VM 3
Web Browser
OWB or MSP
XOG Node 4A-Xmx4096m
App Node 3A-Xmx6144m
BG Node 3A-Xmx4096m
Report Node 3A-Xmx6144m
Report Node 2A-Xmx6144m
Report Node 1A-Xmx6144m
BG Node 2A-Xmx4096m
NETWORK
Bandwidth requirements will vary based on number of users, page configuration and size of documents/projects in the system. CA PPM limits the amount of network resources by compressing the data being sent to the browser from the server using java compression functionality. Chrome, IE, Firefox and Safari can then uncompress the data stream using built‐in gzip functionality. The average page size going over the wire is roughly 7 ‐ 25 kb in size limiting bandwidth requirements. Project and document downloads may represent larger file sizes ranging 100 – 300kb as an average.
DISK SPACE
While transactional data requirements are relatively consistent, storage requirements will vary for Document Management depending on which option is chosen to store documents/attachments. CA PPM provides two options in storing the documents/attachments in the database as a BLOB or on the file system as a binary. We highly recommend storing on the file system/NAS/SAN unless the use of storing attachments is minimal. You can always migrate from the file system to the database, but not vise versa. So it’s important to have a good understanding before moving to the database. The following guidelines/examples below will give you a good idea on what to expect in terms of disk space for data.
Fields are auditable in CA PPM v15.x. Depending on your auditing requirements, this feature will affect the database sizing.
Database Sizing (Raw Transactional Data)
Estimate around 15 GB of data per 1,000 users per year(No fields audited, if fields are setup to be auditable this could grow to 20GB of data per 1,000 users per year). To figure out IOPS, use the following example generated from performance tests with various customer data sets. If we look at 500 active users at any one time as peak load, then you should expect to see roughly 4 million transactions per hour(+/‐ 20%) or 1,200 IOPS (+/‐ 20%). Take this IOPS number and multiply it by the number of 500 active user blocks expected. The read‐write ratio for CA PPM is roughly 60:40 at this peak level. This will provide guidance on the type of SAN/NAS/LUN configuration.
Filestore Sizing (Document Management) Example: 600 (Projects per yr) * 10 (Docs per Project) * 100K (Ave Size of doc) * 3 (Ave number of revisions) = 1.8 GB
As part of our Document Management module, we provide purging capabilities that can control the size of the CA PPM Filestore.
CA PPM r15.x Infrastructure Requirements
CA PPM Data Warehouse
The new Data Warehouse (DWH) feature is optimized specifically for reporting and analytics. The Data Warehouse is installed on a separate schema from the CA PPM database schema. The Data Warehouse is populated at scheduled intervals by a CA PPM job. For customers upgrading to CA PPM 15.x, the following sections provide examples of expected growth rates and loading times based on existing database sizes. Customers also have the option of running the CA PPM 15.x Check‐Install scripts to estimate the size of their DWH will be prior to upgrading.
Industry Resources Teams Assignments Tasks Projects TimesheetsTime Entry
WIPFinancial Plans
Retail_1 50 k 175k 650 k 500 k 12 k 600 k 1.5 m 0 12 kFinancial 364 k 1 m 2 m 8 m 180 k 1.6 m 4.1 m 21 m 560 kServices 146 k 1.6 m 7.2 m 6.6 m 102 k 10 m 26 m 40 k 499IT_1 347 k 5 k 554 32 k 800 0 0 4 m 31
ExpectedGrowthRates
We sampled 10 customer data sets from various industries to get an idea of expected growth rates
FunctionalAreasThatInfluenceGrowth
The following data points outline areas that influenced the size/load of the DWH in the above tables.
