codesite-noreply at google
Oct 26, 2009, 8:36 PM
Post #1 of 3
(320 views)
Permalink
|
|
Issue 620 in cherokee: Reverse Proxy Weighting
|
|
Status: New
Owner: ----
New issue 620 by pubcrawler.com: Reverse Proxy Weighting
http://code.google.com/p/cherokee/issues/detail?id=620
This is a request for feature enhancement in Cherokee.
Currently all information sources in a given pool (in round robin) are
treated uniformly load wise. This works fine as long as the backend
servers fulfilling these requests are of equal CPU and have same resources.
However, many people might have other things running on a given server - or
have a server that has less RAM or slower CPU.
This RFE becomes more relative when backend information source are
application servers doing database and application layer functionality.
As such, interested in seeing a weighting feature of backend servers in an
Information Source pool. This could be a feature to graft onto the round
robin configuration or could be new type of balancer.
Say the following:
Server 1: Quad CPU
Server 2: Dual CPU
Server 3: Single CPU
If we were weighting this load evenly:
Server 1: 4 (or 60% of requests go to this server)
Server 2: 2 (or 30% of ")
Server 3: 1 (or 10% of ")
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
