CRN-DRC Integration Performance Test

April 29, 2010

Performance Test Approach

The team conducted Performance testing from 04/12 - 04/29 to test if the DRC services can handle the CRN policy info requests.

Test Types:
Average Load Test (360 TPH)
Query Policy Claim- Shortpull Query by Claim Number- Longpull

Assumptions:
Testing team assumes that the production load statistics provided by Farmers are correct. The Average load was 180 Transactions per Hour (TPH) for both Shortpull and Longpull. Testing does not need to include calls to DRC Assigned Risk Database as this is not end to end testing. Test will assess Average Transaction Response (ATR) and CPU Performance across 2 Web Spheres, 2 Application Server 1 Database that emulate the Production environment.

Capacity Planning Test (15% growth rate)

Query Policy Claim- Shortpull Query by Claim Number- Longpull

Performance Test Results

The Performance Test yielded positive results even at the maximum range or peak traffic, with no immediate needs for performance-impacting environmental changes:
Test Input Results SLA Criteria Concern

Average Load Test

2 VUsers 709 TPH

90% Response Shortpull = 0.21 at 356 TPH 90% Response Longpull = 0.23 at 353 TPH CPU Avg Performance <= 4% CPU Max Performance = 4 %

Successfully met the SLA

None: Negligible to users

Successfully met the SLA

None: There is room for more traffic; concern only when average makes it into the 60-70% range

Capacity Plan Test ( 15% higher than Average Load Test)

2 VUsers 886 TPH

90% Response Shortpull = 0.15 at 445 TPH 90% Response Longpull = 0.23 at 441 TPH Successfully met the SLA

None:

*TPH Transactions Per Hour