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

Dynamically set Delta Lake driver memory #340

Open
mikix opened this issue Aug 28, 2024 · 0 comments
Open

Dynamically set Delta Lake driver memory #340

mikix opened this issue Aug 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mikix
Copy link
Contributor

mikix commented Aug 28, 2024

Currently, we reserve 4GB of memory for the Delta Lake Java driver stack.

That used to be 1GB and then 2GB and now 4GB, as we dealt with the growing Observation table at BCH.

The hardcoded 4GB is overkill for sites (or even individual tasks) with smaller tables. And updating the hardcoded number for all cases whenever BCH hits a new limit seems bad.

So ideally the ETL would inspect the target table and we'd choose a memory size based on that. Nice and flexible for all cases.

@mikix mikix added the enhancement New feature or request label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant