-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[improvement](jdbc catalog) Modify the maximum number of connections in the connection pool to 30 by default #36720
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](jdbc catalog) Modify the maximum number of connections in the connection pool to 30 by default #36720
Conversation
…in the connection pool to 30 by default
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 40039 ms
|
TPC-DS: Total hot run time: 173739 ms
|
ClickBench: Total hot run time: 30.72 s
|
run buildall |
TPC-H: Total hot run time: 40355 ms
|
TPC-DS: Total hot run time: 170646 ms
|
ClickBench: Total hot run time: 30.68 s
|
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.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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.
LGTM
…in the connection pool to 30 by default (apache#36720) In many cases, we found that users would use JDBC Catalog to perform a large number of queries, which resulted in the maximum of 10 connections being insufficient, so I adjusted it to 30, which covered most needs.
…in the connection pool to 30 by default (apache#36720) In many cases, we found that users would use JDBC Catalog to perform a large number of queries, which resulted in the maximum of 10 connections being insufficient, so I adjusted it to 30, which covered most needs.
…in the connection pool to 30 by default (#36720) In many cases, we found that users would use JDBC Catalog to perform a large number of queries, which resulted in the maximum of 10 connections being insufficient, so I adjusted it to 30, which covered most needs.
…connections in the connection pool to 30 by default (apache#37024) pick (apache#36720) In many cases, we found that users would use JDBC Catalog to perform a large number of queries, which resulted in the maximum of 10 connections being insufficient, so I adjusted it to 30, which covered most needs.
In many cases, we found that users would use JDBC Catalog to perform a large number of queries, which resulted in the maximum of 10 connections being insufficient, so I adjusted it to 30, which covered most needs.