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

Improve memory usage in federated metastore request/response forwards #24

Closed
ddcprg opened this issue Sep 27, 2017 · 0 comments
Closed
Assignees

Comments

@ddcprg
Copy link
Contributor

ddcprg commented Sep 27, 2017

Spike

Overview
At the moment the database mappings create copies of the Thrift objects it processes. Some of these objects can be huge and the creation of copy will demand memory for the request. As we only need the original object to determine which megastore will process the request we could mutate the current object instead of making a copy.

Acceptance criteria
Evaluate memory usage before and after the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant