ThirdEye operates a Create-Run-Transfer Policy to ensure the customer is able to understand and reuse the Performance Test Suite repeatedly.

Application Component Testing:

Performance should be considered before the first line of code is ever written. ThirdEye provides Enterprise Application Services, which will help your development staff, avoid the common performance pitfalls when designing J2EE or Windows based applications. Once the code is at a a point where components or areas of code can be extracted and tested, performance testing should begin. ThirdEye uses a variety of tools to test various "pieces" of your application before the final product is complete. Testing the scalability of COM components, Enterprise Java Beans (EJB's), or web services directly through SOAP calls would be examples of this. Finding performance issues at this stage will save you money and time. By finding most of the performance issues during the development phase, you eliminate time on the back end of the project where time to market dates are critical.

Performance Benchmarking :

Benchmarking provides a model of how the system reacts to an individual Business Processes. Controlled levels of users will be applied to the system and certain performance parameters will be recorded to build the model. This information can then be used as a comparison if changes are made to the infrastructure.

Performance Diagnostics Testing :

If the system is not performing as it should, a set of tests will be designed to identify what is causing the bottleneck.

Performance Tuning Testing :

A set of tests will be designed to identify the optimum configuration for each of the core elements to ensure the maximum performance from the system is reached.

Soak and Reliability Testing :

Soak and Reliability tests will be executed over a prolonged period (usually up to 72 hours) to identify if any of the servers have memory leaks, memory de-allocation issues, the databases to be used are of the correct size, and the system is stable over prolonged periods of time.

Load Testing :

Tests will be executed loading the system with typical daily patterns. This will provide a list of system specifications under a controlled load such as Application Response Time, Bandwidth used, hits per second on the system, Transaction per second carried out by the system.

Stress/Scalability/Capacity Testing :

A set of tests that will identify the maximum number of concurrent users or transactions the system is able to process before the degradation in performance becomes unacceptable.

Spike and Synchronization Testing :

Tests the performance characteristics of the system when all the users are synchronized (Logon is most common).

Failover and Resilience Testing :

Tests to identify how the network, hardware, software, and database elements react when certain components are removed from the system.

Bandwidth Verification :

This will confirm the bandwidth of the pipeline on your site into the application is able to deal with the number of users.

Application Performance Monitoring :

24-7 monitoring of business critical applications post deployment enables identification of potential system failure before users do, preventing down time and loss of revenue. Enforce SLAs and receive warning alerts through continuous performance monitoring from real user perspective.