Difference between revisions of "Test Environment Documentation"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
The hardware resources allocated to each vm will be altered between test runs to create different test configurations. | The hardware resources allocated to each vm will be altered between test runs to create different test configurations. | ||
| + | |||
| + | = Monitoring = | ||
| + | |||
| + | Required metrics: | ||
| + | |||
| + | Operating System - | ||
| + | cpu usage - user, system, idle, waiting | ||
| + | io stats - tps (transactions per second) as well as reads per second, writes per second | ||
| + | memory usage - total memory used, total swap used | ||
| + | |||
| + | Mysql - | ||
| + | total number of connections | ||
| + | mysql memory and cpu usage | ||
| + | mysql buffer cache usage | ||
| + | |||
Back to main [[Scalability_testing]] page. | Back to main [[Scalability_testing]] page. | ||
Revision as of 12:13, 11 January 2013
Testing environment for use in Scalability Testing of Arhcivematica 1.0.
Initial specs:
5 virtual machines set up using kvm. All running XUbuntu 12.04.
- vm1 - running mcp server and mysql
- vm2, vm3, vm4 - running mcp clients
- vm5 - monitor, running munin and/or collectd
The hardware resources allocated to each vm will be altered between test runs to create different test configurations.
Monitoring
Required metrics:
Operating System - cpu usage - user, system, idle, waiting io stats - tps (transactions per second) as well as reads per second, writes per second memory usage - total memory used, total swap used
Mysql - total number of connections mysql memory and cpu usage mysql buffer cache usage
Back to main Scalability_testing page.