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

52 lines
1.4 KiB
TOML
Raw Normal View History

Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
[package]
name = "tower-balance"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
# When releasing to crates.io:
# - Remove path dependencies
# - Update html_root_url.
# - Update doc url
# - Cargo.toml
# - README.md
# - Update CHANGELOG.md.
# - Create "v0.1.x" git tag.
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
version = "0.1.0"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
authors = ["Tower Maintainers <team@tower-rs.com>"]
Add license field to all crates (#241)
2019-04-09 10:59:30 -07:00
license = "MIT"
chore: fix small errors in Cargo files
2019-04-26 22:31:07 -07:00
readme = "README.md"
repository = "https://github.com/tower-rs/tower"
homepage = "https://github.com/tower-rs/tower"
documentation = "https://docs.rs/tower-balance/0.1.0"
description = """
Balance load across a set of uniform services.
"""
categories = ["asynchronous", "network-programming"]
Move Tower to 2018 Edition (#238)
2019-04-08 20:11:09 -07:00
edition = "2018"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
publish = false
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
Early push to bring tracing into tower (#298) Of particular note is that this change lets spans trace requests through `tower::Buffer` by internally carrying the `Span` at the time of `call` along with the request to the worker.
2019-07-12 11:46:50 -07:00
[features]
log = ["tracing/log"]
default = ["log"]
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
[dependencies]
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
futures = "0.1.26"
indexmap = "1.0.2"
Early push to bring tracing into tower (#298) Of particular note is that this change lets spans trace requests through `tower::Buffer` by internally carrying the `Span` at the time of `call` along with the request to the worker.
2019-07-12 11:46:50 -07:00
tracing = "0.1"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
rand = "0.6.5"
balance: Only balance over ready endpoints (#293) In 03ec4aa, the balancer was changed to make a quick endpoint decision. This, however, means that the balancer can return NotReady when it does in fact have a ready endpoint. This changes the balancer to separate unready endpoints, only performing p2c over ready endpoints. Unready endpoints are tracked with a FuturesUnordered that supports eviction via oneshots. The main downside of this change is that the Balancer must become generic over the Request type.
2019-07-05 20:46:33 -07:00
tokio-sync = "0.1.3"
balance: Implement a Peak-EWMA load metric (#76) The balancer provides an implementation of two load balancing strategies: RoundRobin and P2C+LeastLoaded. The round-robin strategy is extremely simplistic and not sufficient for most production systems. P2C+LL is a substantial improvement, but relies exclusively on instantaneous information. This change introduces P2C+PeakEWMA strategy. P2C+PE improves over P2C+LL by maintaining an exponentially-weighted moving average of response latencies for each endpoint so that the recent history directly factors into load balancing decisions. This technique was pioneered by Finagle for use at Twitter. [Finagle's P2C+PE implementation][finagle] was referenced heavily while developing this. The provided demo can be used to illustrate the differences between load balacing strategies. For example: ``` REQUESTS=50000 CONCURRENCY=50 ENDPOINT_CAPACITY=50 MAX_ENDPOINT_LATENCIES=[1ms, 10ms, 10ms, 10ms, 10ms, 100ms, 100ms, 100ms, 100ms, 1000ms, ] P2C+PeakEWMA wall 15s p50 5ms p90 56ms p95 78ms p99 96ms p999 105ms P2C+LeastLoaded wall 18s p50 5ms p90 57ms p95 80ms p99 98ms p999 857ms RoundRobin wall 72s p50 9ms p90 98ms p95 496ms p99 906ms p999 988ms ```` [numbers]: https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html [finagle]: https://github.com/twitter/finagle/blob/9cc08d15216497bb03a1cafda96b7266cfbbcff1/finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/PeakEwma.scala
2018-06-06 23:16:49 -07:00
tokio-timer = "0.2.4"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
tower-discover = "0.1.0"
balance: Specialize the balancer for P2C (#288) As described in #286, `Balance` had a few problems: - it is responsible for driving all inner services to readiness, making its `poll_ready` O(n) and not O(1); - the `choose` abstraction was a hinderance. If a round-robin balancer is needed it can be implemented separately without much duplicate code; and - endpoint errors were considered fatal to the balancer. This changes replaces `Balance` with `p2c::Balance` and removes the `choose` module. Endpoint service failures now cause the service to be removed from the balancer gracefully. Endpoint selection is now effectively constant time, though it biases for availability in the case when random selection does not yield an available endpoint. `tower-test` had to be updated so that a mocked service could fail after advertising readiness.
2019-06-04 13:59:47 -07:00
tower-layer = "0.1.0"
Extract tower-load from tower-balance (#285) The tower-balance crate includes the `Load` and `Instrument` traits, which are likely useful outside of balancers; and certainly have no tight coupling with any specific balancer implementation. This change extracts these protocol-agnostic traits into a dedicated crate. The `Load` trait includes a latency-aware _PeakEWMA_ load strategy as well as a simple _PendingRequests_ strategy for latency-agnostic applications. The `Instrument` trait is used by both of these strategies to track in-flight requests without knowing protocol details. It is expected that protocol-specific crates will provide, for instance, HTTP time-to-first-byte latency strategies. A default `NoInstrument` implementation tracks the a request until its response future is satisfied. This crate should only be published once tower-balance is published. Part of https://github.com/tower-rs/tower/issues/286
2019-05-29 10:32:02 -07:00
tower-load = { version = "0.1.0", path = "../tower-load" }
tower-service = "0.2.0"
Prepare release (#273) The following crates are to be released: - tower - tower-buffer - tower-discover - tower-layer - tower-limit - tower-load-shed - tower-retry - tower-service - tower-test - tower-timeout - tower-util
2019-04-26 21:31:25 -07:00
tower-util = "0.1.0"
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]
Early push to bring tracing into tower (#298) Of particular note is that this change lets spans trace requests through `tower::Buffer` by internally carrying the `Span` at the time of `call` along with the request to the worker.
2019-07-12 11:46:50 -07:00
tracing-fmt = { git = "https://github.com/tokio-rs/tracing.git" }
Fix some simple compile-time warnings (#297)
2019-07-05 14:10:11 -07:00
hdrhistogram = "6.0"
Upgrade to env_logger 0.5 and log 0.4 so that projects that use those (#52) versions don't have to build both those versions and the older ones that h2 is currently using. Don't enable the regex support in env_logger. Applications that want the regex support can enable it themselves; this will happen automatically when they add their env_logger dependency. Disable the env_logger dependency in quickcheck. The result of this is that there are fewer dependencies. For example, regex and its dependencies are no longer required at all, as can be seen by observing the changes to the Cargo.lock. That said, env_logger 0.5 does add more dependencies itself; however it seems applications are going to use env_logger 0.5 anyway so this is still a net gain. Submitted on behalf of Buoyant, Inc. Signed-off-by: Brian Smith <brian@briansmith.org>
2018-02-23 20:24:22 -08:00
quickcheck = { version = "0.6", default-features = false }
balance: Implement a Peak-EWMA load metric (#76) The balancer provides an implementation of two load balancing strategies: RoundRobin and P2C+LeastLoaded. The round-robin strategy is extremely simplistic and not sufficient for most production systems. P2C+LL is a substantial improvement, but relies exclusively on instantaneous information. This change introduces P2C+PeakEWMA strategy. P2C+PE improves over P2C+LL by maintaining an exponentially-weighted moving average of response latencies for each endpoint so that the recent history directly factors into load balancing decisions. This technique was pioneered by Finagle for use at Twitter. [Finagle's P2C+PE implementation][finagle] was referenced heavily while developing this. The provided demo can be used to illustrate the differences between load balacing strategies. For example: ``` REQUESTS=50000 CONCURRENCY=50 ENDPOINT_CAPACITY=50 MAX_ENDPOINT_LATENCIES=[1ms, 10ms, 10ms, 10ms, 10ms, 100ms, 100ms, 100ms, 100ms, 1000ms, ] P2C+PeakEWMA wall 15s p50 5ms p90 56ms p95 78ms p99 96ms p999 105ms P2C+LeastLoaded wall 18s p50 5ms p90 57ms p95 80ms p99 98ms p999 857ms RoundRobin wall 72s p50 9ms p90 98ms p95 496ms p99 906ms p999 988ms ```` [numbers]: https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html [finagle]: https://github.com/twitter/finagle/blob/9cc08d15216497bb03a1cafda96b7266cfbbcff1/finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/PeakEwma.scala
2018-06-06 23:16:49 -07:00
tokio = "0.1.7"
tokio-executor = "0.1.2"
balance: Only balance over ready endpoints (#293) In 03ec4aa, the balancer was changed to make a quick endpoint decision. This, however, means that the balancer can return NotReady when it does in fact have a ready endpoint. This changes the balancer to separate unready endpoints, only performing p2c over ready endpoints. Unready endpoints are tracked with a FuturesUnordered that supports eviction via oneshots. The main downside of this change is that the Balancer must become generic over the Request type.
2019-07-05 20:46:33 -07:00
tower = { version = "*", path = "../tower" }
tower-buffer = { version = "*", path = "../tower-buffer" }
tower-limit = { version = "*", path = "../tower-limit" }
tower-test = { version = "*", path = "../tower-test" }