QA - nGenera Product Load and Performance Needs

Hub

Status: Up to now, the load and performance testing has been limited to some load balancing testing, using a tool called 'HTTPPerf'. The busier Hubs are http://portal.ngenera.com and http://ngenera.com. There is no data regarding the number of concurrent users or actual usage patterns.

Short Term Initiative: Develop and run a generic load test that will establish the maximum load (read 'concurrent users') that the test environment can handle. The sole aim of this test is the figure out if/when we will start running into trouble if the number of our customers starts to increase.

The pre-conditions in order to be able to run this test are:

1. Establish a test site with a configuration that resembles the production environment, or at least as closely as possible (To Do: Mike to coordinate with Scott)
   
2. Create some usage scenarios (To Do: Maarten to check with Steve E.) As an alternative Mike will look into setting up logging in the production environment to see if we can retrieve some actual user usage patterns.
3. Select a temporary tool. This might / might not become part of the coporate load and performance tool(s), so we need to be prepared to eventually 'throw away' the efforts we are putting into this exercise. (ToDo: Mike will check with the Ruby community for popular tools)

Long-term Initiatives: Establish a set of load and performance test objectives

Technology Platform

Status:

Short-term Initiatives:

Long-term Initiatives:

Channels

Status:

Short-term Initiatives:

Long-term Initiatives:

Knowledge Base

Status:

Short-term Initiatives: Develop and run a generic load test that will establish that the users of the customer portal will receive acceptable response times with a peak load of 600 plus concurrent users. The aim of this test is establish a confidence level both internally as well as with the customer base that the release is ready to be deployed to Production after the recent fallback.

1. Test environment: Is ready
2. Usage scenarios: The two usage scenarios that have been identified are the '3 click process' and 'search'
3. Tools: Hamel is researching temporary tools.

Long-term Initiatives: Establish a set of load and performance test objectives

TCS

Status: Load testing on their product was done a while ago.

Short-term Initiatives: I need to figure out more of the details, exactly what was tested and what tool was used.

Long-term Initiatives: Jimmy G's biggest concern is regarding hierarchies (manager/employee) that will need to be supported in the tool when the user base will grow exponetially from 2,500 to 18,000 over the next 6 months or so.