System Resource Utilization Statistics for Cycle
The system resource utilization (JVM utilization) statistics for all the servers obtained for Cycle load tests are given below:
Heap Utilization
The G1 GC policy enabled optimal memory utilization with appropriate GC activity. The heap usage for each instance is between 1 GB and 3 GB out of 4GB allocation. Frequent minor and major GC’s were happened as expected to reclaim young gen memory and decent OLD gen GC’s. There is no instance of Out of Memory issues at all.
Application Servers
Application Server1 CPU Utilization - Average – 5.14 %, Max – 60 %
Below is the graph that shows the CPU utilization of Application Server1 i.e. 5.14 % average utilization has been recorded and went up to 60 % of maximum utilization at the start of the test.
App Server1 Network Utilization
Below is the graph that shows Network utilization of Application Srever1. It can be observed that a series of network reads and writes during the application transaction processing. The average reads are below 1399.3 kb/s and the average writes are below 852.3 kb/s. This indicates the network I/O is decent.
Database Servers
DB Server CPU Utilization - Average – 23.68 %
Below is the graph that shows CPU utilization of a DB server. 23.68% average utilization has been recorded and went up to 90% of maximum utilization.
DB Server Network Utilization
Below is the graph that shows network utilization of a DB server. It can be observed that a series of network reads and writes during the application transaction processing. The average reads are below 1337.5 kb/s and the average writes are below 2374 kb/s. This indicates the network I/O is decent.
Application Tier
Both the JVM memory and CPU on the application server are utilized efficiently. Tuning of application properties, jvm parameters and DB connection pool settings as specified above, gave optimal performance.
Database Tier
Applying indexes, reorganizing of tables with large amounts of data and gathering the schema level statistics before each cycle execution improved the database performance.
create index OIPAPERF.IDX$$_00010001 on OIPAPERF.ASFINANCIALENTRY("ACTIVITYGUID","FINANCIALENTRYGUID","ACTIVETODATE"); create index OIPAPERF.IDX$$_00010031 on OIPAPERF.ASMAPCRITERIA("MAPCRITERIANAME","TEXTVALUE"); create index OIPAPERF.IDX$$_00010031 on OIPAPERF.ASMAPCRITERIA("MAPCRITERIANAME","TEXTVALUE"); dbms_sqltune.accept_sql_profile(task_name => 'SYS_AUTO_SQL_TUNING_TASK', object_id => 10190, task_owner => 'SYS', replace => TRUE); dbms_sqltune.accept_sql_profile(task_name => 'SYS_AUTO_SQL_TUNING_TASK', object_id => 10127, task_owner => 'SYS', replace => TRUE); dbms_sqltune.accept_sql_profile(task_name => 'SYS_AUTO_SQL_TUNING_TASK', object_id => 10224, task_owner => 'SYS', replace => TRUE); |