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

Reduce amount of used ets tables #123

Open
1 of 3 tasks
Strech opened this issue Aug 3, 2024 · 0 comments
Open
1 of 3 tasks

Reduce amount of used ets tables #123

Strech opened this issue Aug 3, 2024 · 0 comments
Labels
enhancement Improvement of existing functionality or request of improvement internal API Anything related to the internal API and implementations

Comments

@Strech
Copy link
Owner

Strech commented Aug 3, 2024

In the current situation, the number of ets tables is proportional to the number of schemas. Every time we parse nested schema we create a new ets schema that goes into recursion.

Despite that fact we already have a cache on top of the schema resolution which is a single place for all schemas after they are resolved we don't leverage it.

It will allow us to reduce coding in related issue #115

TODO

@Strech Strech added enhancement Improvement of existing functionality or request of improvement internal API Anything related to the internal API and implementations labels Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing functionality or request of improvement internal API Anything related to the internal API and implementations
Projects
None yet
Development

No branches or pull requests

1 participant