...
The tools we will employ are yet to be determined. A proof of concept (PoC) is under way on a performance tseting tool. If it is acceptable to MIT then this tool will be identified here. Otherwise furhter PoCs may need to be conducted until a satisfactory tool is identified and accepted by MIT.
3.3 Environmental Needs
We will need the following:
...
A performance test is designed to benchmark the system under test under a realistic load scenario that mimics what we anticipate real world usage will be at its peak. References to non-functional requirements marked as TBD will be updated once the non-functional requirements are provided by MIT.
5.1.1 IDPi Only
The objective of this scenario is to benchmark just the internal IDP.
...
The objective of this scenario is to run both IDPs concurrently for a protracted period of time (multiple days) to determine stbility stability and check for memory leaks. We plan to load the system with 80% of the capacity as determined by the integrated stress test scenario and hold it. During this time special attention wil be paid to memory and general system stability. There should also not be any appreciable deterioration in end-user response times.
5.3.1.1 Load Model
Desired Transaction Rate: TBD80% of capacity
Script | % of Load |
|---|---|
CAMS Account Creation | TBD |
CAMS Association - OpenID | TBD |
CAMS Association - Kerberos | TBD |
Site Access - CAMS Account | TBD |
Site Access - OpenID | TBD |
Site Access - Kerberos w/ticket | TBD |
Site Access - Web Auth | TBD |
...
7.0 Non-functional Requirements
MIT has not yet provided the non-functional Requirements. The link below will be udated if a web page is created to house them, otherwise they will be specified here.
Touchstone Non-functional Requirements
8.0 Architectures
Architectural diagrams will be refenced here as MIT proved them.
8.1 Physical
Touchstone Production Physical Architecture
...
Touchstone Production IdPe Logical Architecture