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.

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

stats: Remove FakeSymbolTableImpl and related helpers #6307

Closed
jmarantz opened this issue Mar 18, 2019 · 10 comments · Fixed by #13392
Closed

stats: Remove FakeSymbolTableImpl and related helpers #6307

jmarantz opened this issue Mar 18, 2019 · 10 comments · Fixed by #13392
Assignees
Labels
no stalebot Disables stalebot from closing an issue tech debt
Milestone

Comments

@jmarantz
Copy link
Contributor

The goal of FakeSymbolTableImpl is to put the SymbolTable API in place. That will enable us to incrementally transform all places in the Envoy codebase where stat-names are constructed to pre-allocate at startup all StatNames constituent strings.

Once the real Symbol TableImpl is in place, encoding strings into symbols requires taking a symbol-table lock, so we don't want to do that in the hot-path.

So FakeSymbolTableImpl allows us to deploy the Symbol API without worrying about lock contention.

Once there are no more hot-path encoding of strings into SymbolTable, we can swap in SymbolTableImpl and delete FakeSymbolTableImpl.

@jmarantz jmarantz self-assigned this Mar 18, 2019
@stale
Copy link

stale bot commented Apr 19, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 19, 2019
@jmarantz
Copy link
Contributor Author

/wait

@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Apr 19, 2019
@stale
Copy link

stale bot commented May 19, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label May 19, 2019
@jmarantz
Copy link
Contributor Author

/wait

@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label May 20, 2019
@stale
Copy link

stale bot commented Jun 19, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Jun 19, 2019
@stale
Copy link

stale bot commented Jun 26, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jun 26, 2019
@zuercher zuercher added no stalebot Disables stalebot from closing an issue and removed stale stalebot believes this issue/PR has not been touched recently labels Aug 8, 2019
@zuercher zuercher reopened this Aug 8, 2019
@mattklein123 mattklein123 added this to the 1.12.0 milestone Aug 11, 2019
@mattklein123 mattklein123 modified the milestones: 1.12.0, 1.13.0 Oct 17, 2019
@mattklein123 mattklein123 modified the milestones: 1.13.0, 1.14.0 Dec 5, 2019
@mattklein123 mattklein123 modified the milestones: 1.14.0, 1.15.0 Mar 18, 2020
@mattklein123
Copy link
Member

I guess we won't be able to clean this up until 1.16 so moving this out.

@mattklein123 mattklein123 modified the milestones: 1.15.0, 1.16.0 Jun 25, 2020
@jmarantz
Copy link
Contributor Author

agreed; we should bake with the default being real symbol tables, but the 'fakes' being available for a release first.

@mattklein123
Copy link
Member

@jmarantz I think we can clean all of the old code up now? WDYT?

@jmarantz
Copy link
Contributor Author

jmarantz commented Oct 5, 2020

Yes, working on it. It's easy to nuke all that code. Hopefully also easy to review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no stalebot Disables stalebot from closing an issue tech debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants