Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Measure performance impact of Envoy's v2 to v3 internal upgrades #9671

Closed
htuch opened this issue Jan 14, 2020 · 2 comments
Closed

Measure performance impact of Envoy's v2 to v3 internal upgrades #9671

htuch opened this issue Jan 14, 2020 · 2 comments
Labels
api/v3 Major version release @ end of Q3 2019 area/perf help wanted Needs help!

Comments

@htuch
Copy link
Member

htuch commented Jan 14, 2020

Now that Envoy is using v3 protos internally, and performing complex wire transformations to move from v2 to v3 during configuration ingestion, there is likely some performance impact. It's unclear whether this is marginal, e.g. single digit percentage, or major. This bug exists to track any learnings here.
@htuch htuch added api/v3 Major version release @ end of Q3 2019 area/perf help wanted Needs help! labels Jan 14, 2020
@htuch htuch mentioned this issue Jan 14, 2020
Merged
@htuch
Copy link
Member Author

htuch commented Jan 14, 2020

CC @mattklein123 @mum4k

@htuch
Copy link
Member Author

htuch commented Jun 9, 2020

This is obviated by #11362.

@htuch htuch closed this as completed Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api/v3 Major version release @ end of Q3 2019 area/perf help wanted Needs help!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@htuch