Mod proxy bybusyness Load Balancing Method: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
This method | This method keeps track of how many requests each worker is currently assigned at present. A new request is automatically assigned to the worker with the lowest number of active requests. This algorithm is is appropriate if the backend nodes queue incoming requests independently, and insures that their request queues are evenly loaded. This way, a request is given to the worker most likely to service it the fastest and reduce latency. Over time, the distribution of work will come to resemble that characteristic of [[Mod proxy byrequests Load Balancing Method|byrequests]]. | ||
Latest revision as of 23:45, 9 January 2017
External
Internal
Overview
This method keeps track of how many requests each worker is currently assigned at present. A new request is automatically assigned to the worker with the lowest number of active requests. This algorithm is is appropriate if the backend nodes queue incoming requests independently, and insures that their request queues are evenly loaded. This way, a request is given to the worker most likely to service it the fastest and reduce latency. Over time, the distribution of work will come to resemble that characteristic of byrequests.