Difference between revisions of "CSE 503S Performance Evaluation Study"
|Line 1:||Line 1:|
Students enrolled in CSE 530S will complete a performance analysis study as part of their final project. The goal of this analysis is to measure the performance of your web
Students enrolled in CSE 530S will complete a performance analysis study as part of their final project. The goal of this analysis is to measure the performance of your web .
== Reading ==
== Reading ==
Revision as of 08:20, 20 August 2021
Students enrolled in CSE 530S will complete a performance analysis study as part of their final project. The goal of this analysis is to measure the performance of your server. These experiments do not need to be performed on your Creative Project. Instead, it is recommended that you focus the performance analysis on the lower-level applications (such as web server and database performance).
The following article will contain information that will help you with this assignment.
You may work alone or with a partner on this assignment.
- Choose two types of experiments to perform on your web server. The types of experiments you should run are largely dependent on the type web application you are developing. Ask the instructor if you are unclear on what types of experiments to perform. Below is a small list of potential experiments to consider.
- Apache web server performance evaluation on different AWS instance types  
- MySQL Performance evaluation on different AWS instance types
- Apache and Nginx comparison on the same AWS instance type 
- MongoDB performance evaluation on different instance types  
- Node.js and Apache+PHP comparison on the same AWS instance type 
- Apache Web Server performance with and without optimizations and tuning 
- PHP performance with and without caching 
- Elastic Load Balancing (ELB) evaluation using several smaller instances vs a single larger instance 
- For each experiment collect data for a range of settings/inputs/configurations and at least two types of data.
- An experiment using Apache Benchmark (ab) would be interested in the pages/sec and the mean time per request
- When evaluating a MySQL database, one could measure both reads/sec and writes/sec to a database
- Create a report that contains a description of your web app, metrics you are interested in, experimental setup, and results
- Provide a discussion of the evaluation and recommendations for deployment. If you are testing on different instance types discuss the cost benefits of a larger instance. (Is an instance that costs 10x that of a smaller instance worth the additional costs?)
This assignment is worth 60 points in total.
- Two Experimental Evaluations (20 Points Per Experiment, 40 Points Total):
- Experimental setup clearly explained (5 pts)
- Experimental results contain multiple data points ( 5 pts)
- At least two different types of data is recorded (6 pts)
- A graph of the experimental results for each type of data recorded (4 pts)
- Write-up (20 Points):
- Detailed discussion of results (10 pts)
- What were the potential bottlenecks of the system? (5 pts)
- What type of instance or configuration would you recommend? (5 pts)