Xen testing
From JJBwiki
Contents |
[edit] Objective
The objective of testing this is to ascertain weather Xen Virtualization technolgy/software is stable and robust enough to use in a production environment. An example of the ideal situation would be to consolidate several smaller (smaller being defined in terms of resource utilization) websites or databases onto one machine. In order to verify how well this will work the system itself needs to be tested for hardware stability, driver level and software stability as well. The way I intend to approach this is from the perspective primarily of a tester, documenting the procedure as I go. Once the proceedure is complete I will write an additional wiki entry regarding Xen administration.
The primary reason for testing xen is to see if we can get the needed functionality (virtualization) at a lower price point. Xen source for testing/PV would be free. Xen enterprise for production is by far and away the cheapest solution for a 2 CPU system.
[edit] Hardware Testing
Most of these testing utilities can be found within the HPC Challenge suite. All tests should run for a minimum of 4 hours.
http://icl.cs.utk.edu/hpcc/ http://ltp.sourceforge.net/
[edit] Memory
STREAM is the industry standard for memory benchmarking. It tests sustainable memory bandwidth.
http://www.cs.virginia.edu/stream/
[edit] Disk I/O
The best bet for this particular test is xdd. dbench and the LTP suite also offer decent efficiency on this front.
http://ltp.sourceforge.net/tooltable.php
[edit] Network
lperf, iperf and the LTP suite offer different types of network testing.
http://ltp.sourceforge.net/tooltable.php
[edit] CPU
Linpack benchmarking is perhaps the best suite to perform CPU based benchmarking. Linpack will also hit the memory fairly hard depending on settings.
http://www.top500.org/about/linpack
[edit] Software Testing
Run all tests for at least 4 hours. Preferably 24 hours.
[edit] Apache
- Setup an apache host inside a VM. Test the apache host by using the seige tool.
- Setup multiple apache hosts inside VM's and test them simultaneously using seige.
http://www.joedog.org/
[edit] Squid
- Setup a single squid host. Test it using web-polygraph.
- Repeat the test process using several VM instances of squid.
http://www.web-polygraph.org/
