-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Use background thread pool for background buffer flushes #10315
Use background thread pool for background buffer flushes #10315
Conversation
@@ -78,6 +78,7 @@ struct Settings : public SettingsCollection<Settings> | |||
M(SettingBool, extremes, false, "Calculate minimums and maximums of the result columns. They can be output in JSON-formats.", IMPORTANT) \ | |||
M(SettingBool, use_uncompressed_cache, true, "Whether to use the cache of uncompressed blocks.", 0) \ | |||
M(SettingBool, replace_running_query, false, "Whether the running request should be canceled with the same id as the new one.", 0) \ | |||
M(SettingUInt64, background_buffer_flush_schedule_pool_size, 16, "Number of threads performing background flush for tables with Buffer engine. Only has meaning at server startup.", 0) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok.
Only has meaning at server startup.
I hope we will separate these kind of settings eventually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I don't understand why they are here and not in server config (i.e. config.xml
)...
Follow-up-for: ClickHouse#10315 Follow-up-for: ClickHouse#10263
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Use background thread pool for background buffer flushes (this will allow to avoid occupation threads when there are no insert's)
Refs: #6833 (comment) (does this resolves this issue after other fixes and this one?)
P.S. I placed some code (settings and changes in context) a little bit "non grouped" to avoid conflicts with #10263