Best Practices for System Performance
<aside> đź’ˇ To download a PDF copy of this TRIRIGAFEEDIA Best Practices Chapter 3: System Architecture & Hardware, click the attachment below.
</aside>
TRIRIGAFEEDIA_3.x.x_Best_Practices_03_System_Architecture_&_Hardware_20200324.pdf
This section addresses ways to maximize system performance by configuring your system architecture to account for your resource needs. Note that when evaluating sizing for your TRIRIGA system, it is important to include a performance test phase as part of the implementation. This section contains sample starting configurations, but it is crucial that performance testing analysis and tuning be conducted to reach the optimal configuration for your unique environmental and application circumstances prior to signing off on the final production configuration.
For more details on system architecture and hardware configuration, see the Installation and Implementation Guide (3.7.0).
As with any web-based platform, the application server and database capacity that is needed to deploy the TRIRIGA system implementation depends largely on the number of anticipated users and user requests.
The limits of what is needed are determined by how users are expected to use the system. At a minimum, the server capacity to satisfy the average load during a work day is required, with response times that are acceptable to the user base. If possible, aim to satisfy the volume of requests that is anticipated during peak intervals of high user activity. Hardware resources such as CPU, memory, I/O capacity, and network bandwidth are key to reducing response times. Unless you install TRIRIGA on a server or group of servers that can handle a large number of transactions, users are probably going to experience slow response times.
Adding more servers and database capacity can sometimes improve TRIRIGA performance, but that is not always the case. The application usage and system configuration can play a significant role in the balance of system performance.
Estimating the TRIRIGA system size can be a complex and error-prone process. That’s why it's called an estimation, rather than a calculation. There are two primary estimation methodologies to sizing a TRIRIGA implementation: (1) Size by Example, and (2) Proof of Concept.
A Size by Example (SBE) approach requires a set of known samples to use as data points along the range of system sizes. By making more examples available for SBE, the intended implementation will be more accurate. Several targeted SBE sizing solutions for prospective TRIRIGA customers are provided below. These targeted solutions were compiled from our internal deployments, performance benchmarks, and our customers' external deployments.