ITX8080
Schedule
Lecture TH 12:00 - 13:30
Practice FR 14:00 - 17:30
Communication
Discussinons will be held at: itx8080 atatat googlegroups.com
Send e-mail to hannesa at-no-spam-please gmail.com for an invitation.
The lecturers can be reached via the course coordinator:
antti.andreimann only-people-please eesti.ee
Points awarded so far
Arnis : 1 point
Igor : 1 point
Scenario 1
There is a Wordpress based blog.
The client is worried: How many visitors can they handle before they die.
Establish a baseline: How many page displays per second AT LEAST we can handle. Disruption of the site operation is NOT acceptable.
Minimal budget!
Be as detailed and technical as You possibly can.
Post to the discussion group the following information:
- Detailed description of the simulation of the site. eg. if You're going to virtualize it then how? If You are running it as a process, then how You separate it from the real machine?
- Detailed description of the attack / benchmark tools picked. Where You are going to run them? What tools? How many copies? How you are going to collect the results?!!!
Proposals
Benchmarking:
* AB - Discussed in lecture * http://tsung.erlang-projects.org - Jérémy Gagnard * wget + AB - Arnis Parsovs * http://jakarta.apache.org/jmeter/ - Roland Vares, Jérémy Gagnard * http://grinder.sourceforge.net/ - Märt Võhni * http://httpd.apache.org/test/flood/ - Hannes Aavaste * Normal monitoring software on live server - Urmas
Simulation of the system:
* VirtualBox - Roland Vares, Jérémy Gagnard * VMWare ESX - Igor Maksimov * VMWare Player - Marina * Amazon EC2 - Märt Võhni * KVM - Siim Adamson * Original hardware - Hannes Aavaste
Scenario 2
Design a method for evaluating any speedup solutions for the wordpress. A repeatable process to evaluate the claims. Whatever optimizations. The process must be detailed enough so that somebody else can get the same results when applying that. The @other person@ is expected to have IT knowledge sufficient to install and run a Linux desktop. The method must specify the level performance at which the site is considered DEAD. Budget requirements: Low - Dedicated machine + dedicated tester.