Your simulation structure should be event-driven simulation, which is the most common simulation model. At any given time, the simulation is in a single state. The simulation state can ONLY change at event times, where an event is defined as an occurrence that MAY change the state of the system. Events in this CPU simulation are the following: process arrival and the transition of a process state (e.g., when an interrupt occurs due to a time slice, the process moves from running state to ready state).
Each event occurs at a specified time. Since the simulation state only changes at an event, the clock can be advanced to the next most recently scheduled event. (Thus the term next event simulation model.)
Events are scheduled via an event queue. The event queue is a sorted queue which contains "future" events; the queue is sorted by the time of these "future" events. The event queue is initialized to contain the arrival of the processes and the first occurrence of the timer interrupt. The main loop of the simulation consists of processing the next event, perhaps adding more future events in the queue as a result, advancing the clock, and so on until all processes terminate.
In the end, you should compare the following scheduling policy:
1. First Come First Serve
2. Shortest Job First, without preemption
3. Shortest Job First, or shortest-remaining-time-first; preemption 4. Round Robin, with the quantum 10.
5. Round Robin, with time quantum 50.
6. Round Robin, with time quantum 100.
and for more details
please read the document completely and carefully you need to full fill all the requirements in the document and you need you do each and every module in the document
Décerné à :
4 freelance font une offre moyenne de $61 pour ce travail
I am interested in this project and so wanted to discuss more about it in details. Please initiate a message to me so that we can discuss. Looking forward to having long term business relationship Thanks