Web Application Performance: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
* Document the procedures to stop/start the processes - some load tests may need the processes to be completed shut down and restarted. Usually there's an "Environment" document associate with the environment where all these procedures are documented. | * Document the procedures to stop/start the processes - some load tests may need the processes to be completed shut down and restarted. Usually there's an "Environment" document associate with the environment where all these procedures are documented. | ||
* If the target are Windows machines, it's a good idea to install Cygwin - it'll improve productivity and provide a lot of good tools. | * If the target are Windows machines, it's a good idea to install Cygwin - it'll improve productivity and provide a lot of good tools. | ||
* Annotate the environment diagram with the RAM and CPU amount on each host. | |||
Revision as of 01:17, 13 January 2016
Internal
Methodology
Set up the performance testing environment.
Map it (Performance Testing Environment.odg)- get a diagram that shows:
- Hosts (names, IP addresses/subnet masks, external ports).
- Represent all network interfaces and their connectivity to various networks. It helps to understand how the hosts are interconnected - on the diagram.
- Represent processes
- Load Agent
- Proxy
- Application Server
- Database
- Document the procedures to stop/start the processes - some load tests may need the processes to be completed shut down and restarted. Usually there's an "Environment" document associate with the environment where all these procedures are documented.
- If the target are Windows machines, it's a good idea to install Cygwin - it'll improve productivity and provide a lot of good tools.
- Annotate the environment diagram with the RAM and CPU amount on each host.