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

[Improvement]: Make the maximum input file size for per optimize thread configurable #2385

Closed
3 tasks done
Tracked by #2176
hameizi opened this issue Nov 30, 2023 · 0 comments · Fixed by #2387
Closed
3 tasks done
Tracked by #2176

Comments

@hameizi
Copy link
Contributor

hameizi commented Nov 30, 2023

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

Currently, the maximum input file size for each optimize thread is fixed at 512MB. When processing tables with rapidly generated data, having a single optimize thread handle fewer files can cause the optimization merging speed to fall behind the rate at which the table is generating files. In cases where concurrent resources for optimization are sufficient, increasing the number of files processed by a single optimize thread can effectively address this issue.

How should we improve?

Make the maximum input file size for per optimize thread configurable

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

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

Successfully merging a pull request may close this issue.

1 participant