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

[client-v2] Add property for network buffer size #1784

Merged
merged 4 commits into from
Aug 23, 2024

Conversation

chernser
Copy link
Contributor

Summary

Adds a property to configure a buffer that is used to read data from a socket

Checklist

Delete items not relevant to your PR:

  • Unit and integration tests covering the common scenarios were added
  • A human-readable description of the changes was provided to include in CHANGELOG
  • For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

@chernser chernser added this to the 0.6.5 milestone Aug 22, 2024
@chernser chernser requested review from mzitnik and Paultagoras and removed request for mzitnik August 22, 2024 22:04
Copy link

@@ -181,6 +186,15 @@ private HttpClientConnectionManager poolConnectionManager(SSLContext sslContext,
connMgrBuilder::setMaxConnPerRoute);


int networkBufferSize = MapUtils.getInt(chConfiguration, "client_network_buffer_size");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we store the key as a property somewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, we have a story about it.

@@ -816,6 +829,10 @@ private Map<String, String> setDefaults(Map<String, String> userConfig) {
userConfig.put("connection_ttl", "-1");
}

if (!userConfig.containsKey("client_network_buffer_size")) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be a property somewhere? In case we need to update it...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, we have a story about it.

@chernser chernser merged commit c49d5a2 into main Aug 23, 2024
57 of 59 checks passed
@chernser chernser deleted the clientv2_perf_record_map_optimization branch August 23, 2024 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants