RIGHTNOW A C E 2 0 1 4 2014 Aras 1
A C E 2 0 1 4 Scalability Test Projects Understanding the results 2014 Aras
Overview Original Use Case Scalability vs Performance Scale to? Scaling the Database Server Scaling the Application Server 2014 Aras 3
Original Use Case If the Aras Innovator instance has 500,000 named users in the system and approximately 100,000 concurrent users, how do you scale SQL Server to meet the demand? 40 core Intel Xeon E7-4870, 2.4 GHz 256 GB RAM I/O subsystem options by load: Between 75,000 and 125,000 concurrent users: Two HP StorageWorks Disk Enclosure D2700s, with 25 drives each to spread out I/O load. This will require a second smart array controller. For complete in-chassis storage at this level of usage we recommend a pair of Fusion-io 2 DUO cards. For high availability, we recommend using a shared storage cluster solution such as: MSA 2040 or HP 3Par 7200 directly attached to a DL980 cluster. One 1/10 Gb NIC with four ports, or a comparable network interface that matches this level of performance. In general, we recommend using one 1Gb NIC per 30,000 concurrent users, and to not exceed 15,000 packets per second on a single Gb link. 2014 Aras 4
Scalability vs Performance Client Application Server Database Server 2014 Aras 5
Scalability vs Performance Scalability 2014 Aras 6
Scalability vs Performance Performance 2014 Aras 7
Performance Large Data Sets SQL Server 2012 is recommended with the release of Aras Innovator 10 Easiest/fastest way to improve performance is to add RAM if SQL Server is the bottleneck SQL Server should never be Express Edition Latency With every version of Aras Innovator we increase the sophistication of the client caching mechanisms Staying current with service packs containing performance enhancements for dealing with latency is highly recommended Bandwidth IIS compression can be used to decrease the size of the data being transferred, and thus utilizing less bandwidth ItemTypes can to be designed to return smaller amounts of data, where possible, allowing for faster load times In some cases, customers have developed custom client pages to accomplish atomic tasks, like activity voting, so that the full client does not need to load File Transfer Vault Replication allows the transfer of files to local vaults in other parts of the world to improve performance and address bandwidth issues IIS throttling and replication scheduling can be used to optimize replication timing to prevent using too much bandwidth when end users would be impacted Configuring User Read Priority ensure files are requested from the first available vault according to rules for that User s expected performance Client and Network Virus scanners, firewalls, and proxy servers can all intercept requests and cause unintended performance issues These require configuration of the respective tool by IT 2014 Aras 8
Scale to me? The white paper describes the best practices for deploying Aras Innovator 10 on SQL Server 2012 Enterprise Edition deployments with expected workloads ranging in size from less than 25,000 users to over 100,000 users Question: What if you have 1000 users or less? 2014 Aras 9
Scaling the Database Server (CPU) CPUs Recommend for up to 1000 users: 32 logical cores Minimum for up to 250 users: 16 logical cores Logical vs Physical Cores 2014 Aras 10
Scaling the Database Server (Memory) RAM Recommend for up to 1000 users: 64 GB RAM Minimum for up to 250 users: 32 GB RAM Size of the database has a greater influence on RAM requirements than number of users * The most common recommendation from Aras Support to improve performance is to increase RAM 2014 Aras 11
Scaling the Database Server (Disks) Recommend RAID using 4 to 6 physically separate disks For best performance disks should be higher than 1000 IOPS Disk speed impacts performance of concurrent users The following recommended guideline is a good price/performance compromise: Operating System disk(s) could be RAID 1 SQL Server data files (RAID 5 array, minimum of 3 drives) SQL Server log files (RAID 1 array, 2 drives) 2014 Aras 12
Scaling the Database Server (Configuration) SQL Server Enterprise Edition vs other File Distribution Operating System and Virtual Memory Database Engine Data Files and Log Files Temp Databases Temp Databases There should be 1 temp database per physical core up to but NOT more than 8 temp database Not correlated per number of users 2014 Aras 13
Scaling the Application Server We have shown SQL Server Scales Up IIS Scales Up before it Scales Out Vault Server Scales Out before it Scales Up Conversion server scales based on the application it is running 2014 Aras 14
Scaling the Application Server Client Application Server Database Server 2014 Aras 15
Scaling the Application Server IIS Cluster Scale out 2014 Aras 16
Scaling the Application Server Load Balancer Client Affinity 2014 Aras 17
Scaling the Application Server CPU Recommend for up to 1000 users 8 physical cores and 16 logical cores Minimum for up to 250 users 4 physical cores and 8 logical cores Memory Recommend for up to 1000 users 32 GB RAM Minimum for up to 250 users 16 GB RAM HDD IOPS not as critical 2014 Aras 18
RIGHTNOW Go to the Aras website and download the whitepapers on the scalability project Aras Scalability Benchmark Methodology and Performance Results http://www./plm-software/?n=report-aras-scalability-benchmark-methodology-results Aras Database Server Configuration Best Practices http://www./plm-software/?n=report-aras-database-server-configuration-best-practices Review the database server hardware and configuration CPU RAM HDD 2014 Aras 19
RIGHTNOW A C E 2 0 1 4 2014 Aras 20