Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

smarter load balancer polling #40

Open
olix0r opened this issue Apr 19, 2017 · 1 comment
Open

smarter load balancer polling #40

olix0r opened this issue Apr 19, 2017 · 1 comment

Comments

@olix0r
Copy link
Member

olix0r commented Apr 19, 2017

Currently, we check all connections each time the load balancer is polled. This is inefficient, especially as the number of active connections increases. As the docs explain, we can be much more efficient about checking only relevant updates.
olix0r added a commit that referenced this issue Jun 10, 2017
@olix0r
Rewrite linkerd-tcp
ea507f7 
linkerd-tcp 0.1.0 constitues a major rewrite.

Previously, linkerd-tcp did not properly utilize tokio's task model, which lead
to a number of performance and correctness problems. Furthermore, linkerd-tcp's
configuration interface was substantially different from linkerd's, which
caused some confusion.

Now, linkerd-tcp has been redesigned:
- to better-leverage tokio's reactor;
- to support connection and stream timeouts;
- to provide much richer metrics insight;
- to be structured like a linkerd-style router;
- general correctness improvements.

Fixes #26 #40 #49 #50
Depends on linkerd/tacho#20
@olix0r olix0r mentioned this issue Jun 10, 2017
Merged
olix0r added a commit that referenced this issue Jun 13, 2017
@olix0r
Rewrite linkerd-tcp (#63)
323c9f8 
linkerd-tcp 0.1.0 constitutes a major rewrite.

Previously, linkerd-tcp did not properly utilize tokio's task model, which lead
to a number of performance and correctness problems. Furthermore, linkerd-tcp's
configuration interface was substantially different from linkerd's, which
caused some confusion.

Now, linkerd-tcp has been redesigned:
- to better-leverage tokio's reactor;
- to support connection and stream timeouts;
- to provide much richer metrics insight;
- to be structured like a linkerd-style router;
- general correctness improvements.

Fixes #26 #40 #49 #50
Depends on linkerd/tacho#20
@tamird
Copy link
Contributor

tamird commented Jun 17, 2017

@olix0r this should have been closed by ea507f7.

FYI this doesn't do what you think:

Fixes #1 #2 #3"

Each issue needs its own "fixes":

Fixes #1
Fixes #2
Fixes #3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olix0r @tamird