zecfoundation
/
tower
mirror of https://github.com/ZcashFoundation/tower.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tower/tower-balance/Cargo.toml

22 lines
425 B
TOML
Raw Normal View History

Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
[package]
name = "tower-balance"
version = "0.1.0"
authors = ["Carl Lerche <me@carllerche.com>"]
Prevent accidental publishing of the crates
2017-11-16 09:40:32 -08:00
publish = false
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
[dependencies]
futures = "0.1"
Add an examples that demonstrates p2c & rr behavior (#39) The new _demo_ example sends a million simulated requests through each load balancer configuration and records the observed latency distributions. Furthermore, this fixes a critical bug in `Balancer`, where we did not properly iterate through not-ready nodes. * Use (0..n-1).rev() to iterate from right-to-left
2018-01-25 12:51:33 -08:00
log = "0.3"
Make tower-balance load-aware (#35) Previously, tower-balance used a fixed round-robin strategy for load distribution. This change makes `Balance` generic over its load metric and selection strategy. The following new traits have been introduced to satisfy this: - `tower_balance::Load` provides a concrete load metric (i.e. for a service); - `tower_balance::Choose` provides a strategy for selecting a node; There are two load balancing configurations supported out-of-the-box: - `tower_balance::round_robin` provides a load-ignorant round-robin balancer. - `tower_balance::power_of_two_choices` uses the Power of Two Choices to distribute requests to the least-loaded node. This should be used in conjunction with `tower_balance::load::WithPendingRequests` to decorate a `Discover` instance so that all services it produces implement `Load`.
2018-01-24 12:18:12 -08:00
rand = "0.4"
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
tower = { version = "0.1", path = "../" }
tower-discover = { version = "0.1", path = "../tower-discover" }
ordermap = "0.2"
Make tower-balance load-aware (#35) Previously, tower-balance used a fixed round-robin strategy for load distribution. This change makes `Balance` generic over its load metric and selection strategy. The following new traits have been introduced to satisfy this: - `tower_balance::Load` provides a concrete load metric (i.e. for a service); - `tower_balance::Choose` provides a strategy for selecting a node; There are two load balancing configurations supported out-of-the-box: - `tower_balance::round_robin` provides a load-ignorant round-robin balancer. - `tower_balance::power_of_two_choices` uses the Power of Two Choices to distribute requests to the least-loaded node. This should be used in conjunction with `tower_balance::load::WithPendingRequests` to decorate a `Discover` instance so that all services it produces implement `Load`.
2018-01-24 12:18:12 -08:00
[dev-dependencies]
Add an examples that demonstrates p2c & rr behavior (#39) The new _demo_ example sends a million simulated requests through each load balancer configuration and records the observed latency distributions. Furthermore, this fixes a critical bug in `Balancer`, where we did not properly iterate through not-ready nodes. * Use (0..n-1).rev() to iterate from right-to-left
2018-01-25 12:51:33 -08:00
log = "0.3"
env_logger = "0.4"
hdrsample = "6.0"
tokio-core = "^0.1.12"
tokio-timer = "0.1"
Make tower-balance load-aware (#35) Previously, tower-balance used a fixed round-robin strategy for load distribution. This change makes `Balance` generic over its load metric and selection strategy. The following new traits have been introduced to satisfy this: - `tower_balance::Load` provides a concrete load metric (i.e. for a service); - `tower_balance::Choose` provides a strategy for selecting a node; There are two load balancing configurations supported out-of-the-box: - `tower_balance::round_robin` provides a load-ignorant round-robin balancer. - `tower_balance::power_of_two_choices` uses the Power of Two Choices to distribute requests to the least-loaded node. This should be used in conjunction with `tower_balance::load::WithPendingRequests` to decorate a `Discover` instance so that all services it produces implement `Load`.
2018-01-24 12:18:12 -08:00
quickcheck = "0.6"