Fork–join queue

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:Fork-join-queue.svg
A fork–join queueing node

In queueing theory, a discipline within the mathematical theory of probability, a fork–join queue is a queue where incoming jobs are split on arrival for service by numerous servers and joined before departure.[1] The model is often used for parallel computations[2] or systems where products need to be obtained simultaneously from different suppliers (in a warehouse or manufacturing setting).[3]:78–80 The key quantity of interest in this model is usually the time taken to service a complete job. The model has been described as a "key model for the performance analysis of parallel and distributed systems."[4] Few analytical results exist for fork–join queues, but various approximations are known.

The situation where jobs arrive according to a Poisson process and service times are exponentially distributed is sometimes referred to as a Flatto–Hahn–Wright model or FHW model.[5][6][7]

Definition

On arrival at the fork point, a job is split into N sub-jobs which are served by each of the N servers. After service, sub-job wait until all other sub-jobs have also been processed. The sub-jobs are then rejoined and leave the system.[3]

For the fork–join queue to be stable the input rate must be strictly less than sum of the service rates at the service nodes.[8]

Applications

Fork–join queues have been used to model zoned RAID systems,[9] parallel computations[2] and for modelling order fulfilment in warehouses.[3]

Response time

The response time (or sojourn time[10]) is the total amount of time a job spends in the system.

Distribution

Ko and Serfozo give an approximation for the response time distribution when service times are exponentially distributed and jobs arrive either according to a Poisson process[11] or a general distribution.[12] QIu, Pérez and Harrison give an approximation method when service times have a phase-type distribution.[13]

Average response time

An exact formula for the average response time is only known in the case of two servers (N=2) with exponentially distributed service times (where each server is an M/M/1 queue). In this situation, the response time (total time a job spends in the system) is[14]

\frac{12-\rho}{8\mu(1-\rho)}

where

  • \rho=\lambda/\mu is the utilization.
  • \lambda is the arrival rate of jobs to all the nodes.
  • \mu is the service rate across all the nodes.

In the situation where nodes are M/M/1 queues and N > 2, Varki's modification of mean value analysis can also be used to give an approximate value for the average response time.[15]

For general service times (where each node is an M/G/1 queue) Baccelli and Makowski give bounds for the average response time and higher moments of this quantity both in the transient and steady state situations.[16] Kemper and Mandjes show that for some parameters these bounds are not tight and show demonstrate an approximation technique.[10] For heterogeneous fork-join queues (fork-join queues with different service times), Alomari and Menasce propose an approximation based on harmonic numbers that can be extended to cover more general cases such as probabilistic fork, open and closed fork-join queues.[17]

Subtask dispersion

The subtask dispersion, defined to be the range of service times, can be numerically computed and optimal deterministic delays introduced to minimize the range.[18]

Stationary distribution

In general the stationary distribution of the number of jobs at each queue is intractable.[11] Flatto considered the case of two servers (N=2) and derived the stationary distribution for the number of jobs at each queue via uniformization techniques.[5] Pinotsi and Zazanis show that a product form solution exists when arrivals are deterministic as the queue lengths are then independent D/M/1 queues.[7]

Heavy traffic/diffusion approximation

When the server is heavily loaded (service rate of the queue is only just larger than arrival rate) the queue length process can be approximated by a reflected Brownian motion which converges to the same stationary distribution as the original queueing process.[19][20] Under limiting conditions the state space of the synchronisation queues collapses and all queues behave identically.[21]

Join queue distribution

Once jobs are served, the parts are reassembled at the join queue. Nelson and Tantawi published the distribution of the join queue length in the situation where all servers have the same service rate.[14] Heterogeneous service rates and distribution asymptotic analysis are considered by Li and Zhao.[22]

Networks of fork–join queues

An approximate formula can be used to calculate the response time distribution for a network of fork–join queues joined in series (one after the other).[23]

Split–merge model

A related model is the split–merge model, for which analytical results exist.[2][24] Exact results for the split-merge queue are given by Fiorini and Lipsky. [25] Here on arrival a job is split into N sub-tasks which are serviced in parallel. Only when all the tasks finish servicing and have rejoined can the next job start. This leads to a slower response time on average.

Generalized (n,k) fork-join system

A generalization of the fork-join queueing system is the (n,k) fork-join system where the job exits the system when any  k out of n tasks are served. The traditional fork-join queueing system is a special case of the  (n,k) system when  k = n . Bounds on the mean response time of this generalized system were found by Joshi, Liu and Soljanin. [26] [27]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.