Topics in Performance Evaluation – Exercise 10

Topics in Performance Evaluation

Exercise 10 – Back to Event-Driven Simulation

We have used event-driven simulation in several exercises. In this one we try to understand its behavior better.

Background

This exercise is actually based on the initial code you may have written in Ex2a. If you didn't, now is the time to make it up. The basic engine is the same, but the simulated system is a bit more involved.

Assignment

  1. If you somehow do not yet have a basic event driven simulator, write one now.
  2. Build the following simulation that uses it. This is similar to a simple M/M/1 simulation, but the details are different. All the constants mentioned here should be parameters, as you will need to make several runs and change them.
  3. Run several simulations, where the difference is the probability p (and hence the expected number of requests that each user makes). Specifically, use p = 0.1, 0.2, 0.3, ... 0.9. What is the resulting average session length as a function of p? What is the utilization of the server as a function of p? Did you get what you expected?
  4. Run the whole set again with a longer simulation – a total of 100 hours, and 1000 users (i.e. 10 times longer). Collect the same results and compare.
  5. Your main task, apart from writing the simulation, is to understand what is going on. Is everything OK? Does a longer simulation provide more accurate results?

Submit

Use Moodle to submit a report on your work, in pdf format, with the following data.

  1. Your names, logins, and IDs
  2. All the outputs in an orderly manner, i.e. tables and/or graphs. Include the average session length and utilization as a function of p for both the short and long simulations. If there are any other metrics that are interesting to follow include them too.
  3. Comment on the results. Do you have anything to say? Are you happy with them?
  4. Speculate on what would happen if the simulation was completely "open system", and all the arrivals in each session were created in advance rather then being created piecemeal during the simulation.
  5. An appendix with the simulation code for all cases.
Submission deadline is Monday, 9 June 2014, so I can give feedback in class on Tuesday.

To the course home page