Round-robin scheduling

<h2 id="process-scheduling">Process scheduling</h2>
<p> 
To <a href="/facts/Process_scheduler/XptmcM1a">schedule processes</a> fairly, a round-robin scheduler generally employs <a href="/facts/Time-sharing/LE5XT9Go">time-sharing</a>, giving each job a time slot or <i>quantum</i><a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> (its allowance of CPU time), and interrupting the job if it is not completed by then. The job is resumed next time a time slot is assigned to that process. If the process terminates or changes its state to waiting during its attributed time quantum, the scheduler selects the first process in the ready queue to execute. In the absence of time-sharing, or if the quanta were large relative to the sizes of the jobs, a process that produced large jobs would be favored over other processes.
</p><p>Round-robin algorithm is a pre-emptive algorithm as the scheduler forces the process out of the CPU once the time quota expires.
</p><p>For example, if the time slot is 100 milliseconds, and <i>job1</i> takes a total time of 250 ms to complete, the round-robin scheduler will suspend the job after 100 ms and give other jobs their time on the CPU. Once the other jobs have had their equal share (100 ms each), <i>job1</i> will get another allocation of <a href="/facts/CPU/Jxp1bqMV">CPU</a> time and the cycle will repeat. This process continues until the job finishes and needs no more time on the CPU. 
</p>
<ul><li>Job1 = Total time to complete 250 ms (quantum 100 ms).</li></ul>
<ol><li>First allocation = 100 ms.</li>
<li>Second allocation = 100 ms.</li>
<li>Third allocation = 100 ms but <i>job1</i> self-terminates after 50 ms.</li>
<li>Total CPU time of <i>job1</i> = 250 ms</li></ol>
<p>Consider the following table with the arrival time and execute time of the process with the quantum time of 100 ms to understand the round-robin scheduling:
</p>
<table><tbody><tr><th>Process name</th><th>Arrival time</th><th>Execute time</th></tr><tr><td>P0</td><td>0</td><td>250</td></tr><tr><td>P1</td><td>50</td><td>170</td></tr><tr><td>P2</td><td>130</td><td>75</td></tr><tr><td>P3</td><td>190</td><td>100</td></tr><tr><td>P4</td><td>210</td><td>130</td></tr><tr><td>P5</td><td>350</td><td>50</td></tr></tbody></table>

<p>Another approach is to divide all processes into an equal number of timing quanta such that the quantum size is proportional to the size of the process. Hence, all processes end at the same time.
</p>
<h2 id="network-packet-scheduling">Network packet scheduling</h2>
<p class="note">Main article: <a href="/facts/Network_scheduler/7URA71LE">Network scheduler</a></p>
<p>In <a href="/facts/Best-effort/W0JBRbtH">best-effort</a> <a href="/facts/Packet_switching/olDlDP1R">packet switching</a> and other <a href="/facts/Statistical_multiplexing/rLGcaGHV">statistical multiplexing</a>, round-robin scheduling can be used as an alternative to <a href="/facts/First-come_first-served/8NDl56EM">first-come first-served</a> queuing.
</p><p>A multiplexer, switch, or router that provides round-robin scheduling has a separate queue for every data flow, where a data flow may be identified by its source and destination address. The algorithm allows every active data flow that has data packets in the queue to take turns in transferring packets on a shared channel in a periodically repeated order. The scheduling is <a href="/facts/Work-conserving_scheduler/u0jd6Cag">work-conserving</a>, meaning that if one flow is out of packets, the next data flow will take its place. Hence, the scheduling tries to prevent link resources from going unused.
</p><p>Round-robin scheduling results in <a href="/facts/Max-min_fairness/vbpvTzIN">max-min fairness</a> if the data packets are equally sized, since the data flow that has waited the longest time is given scheduling priority. It may not be desirable if the size of the data packets varies widely from one job to another. A user that produces large packets would be favored over other users. In that case <a href="/facts/Fair_queuing/hwv3AIud">fair queuing</a> would be preferable.
</p><p>If guaranteed or differentiated quality of service is offered, and not only best-effort communication, <a href="/facts/Deficit_round_robin/exc9lWIz">deficit round-robin</a> (DRR) scheduling, <a href="/facts/Weighted_round_robin/kS83Qt57">weighted round-robin</a> (WRR) scheduling, or <a href="/facts/Weighted_fair_queuing/DU2FCx3p">weighted fair queuing</a> (WFQ) may be considered.
</p><p>In <a href="/facts/Multiple_access/CdCGxpcu">multiple-access</a> networks, where several terminals are connected to a shared physical medium, round-robin scheduling may be provided by <a href="/facts/Token_passing/9cw7bA4f">token passing</a> <a href="/facts/Channel_access/CdCGxpcu">channel access</a> schemes such as <a href="/facts/Token_Ring/mfQj6GSx">Token Ring</a>, or by <a href="/facts/Polling_(computer_science)/WVa88JIg">polling</a> or resource reservation from a central control station.
</p><p>In a centralized wireless packet radio network, where many stations share one frequency channel, a scheduling algorithm in a central base station may reserve time slots for the mobile stations in a round-robin fashion and provide fairness. However, if <a href="/facts/Link_adaptation/vegwIxN8">link adaptation</a> is used, it will take a much longer time to transmit a certain amount of data to "expensive" users than to others since the channel conditions differ. It would be more efficient to wait with the transmission until the channel conditions are improved, or at least to give scheduling priority to less expensive users. Round-robin scheduling does not utilize this. Higher throughput and <a href="/facts/System_spectrum_efficiency/GaePAvv9">system spectrum efficiency</a> may be achieved by channel-dependent scheduling, for example a <a href="/facts/Proportionally_fair/sJgHheRp">proportionally fair</a> algorithm, or <a href="/facts/Maximum_throughput_scheduling/Y0DsAXTU">maximum throughput scheduling</a>. Note that the latter is characterized by undesirable <a href="/facts/Scheduling_starvation/E9UjtIWS">scheduling starvation</a>. This type of scheduling is one of the very basic algorithms for Operating Systems in computers which can be implemented through a circular queue data structure.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Multilevel_queue/GbVSpR9V">Multilevel queue</a></li>
<li><a href="/facts/SCHED_RR/dlkduHuA">SCHED_RR</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Arpaci-Dusseau, Remzi H.; Arpaci-Dusseau, Andrea C. (2014), Operating Systems: Three Easy Pieces [Chapter: Scheduling Introduction] (PDF), Arpaci-Dusseau Books <a href="http://pages.cs.wisc.edu/~remzi/OSTEP/cpu-sched.pdf" target="_blank">http://pages.cs.wisc.edu/~remzi/OSTEP/cpu-sched.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Guowang Miao, Jens Zander, Ki Won Sung, and Ben Slimane, Fundamentals of Mobile Data Networks, Cambridge University Press, ISBN 1107143217, 2016. <a href="/wiki/Guowang_Miao" target="_blank">/wiki/Guowang_Miao</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Stallings, William (2015). Operating Systems: Internals and Design Principles. Pearson. p. 409. ISBN 978-0-13-380591-8. <a href="978-0-13-380591-8" target="_blank">978-0-13-380591-8</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>Silberschatz, Abraham; Galvin, Peter B.; Gagne, Greg (2010). "Process Scheduling". Operating System Concepts (8th ed.). John Wiley & Sons (Asia). p. 194. ISBN 978-0-470-23399-3. 5.3.4 Round Robin Scheduling <a href="978-0-470-23399-3" target="_blank">978-0-470-23399-3</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
</ol>

Round-robin scheduling open-in-new

Round-robin scheduling