[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320509#comment-16320509 ]
ASF GitHub Bot commented on IGNITE-7191: ---------------------------------------- GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3353 IGNITE-7191 JDBC: set socket buffer to 64k by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7191 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3353.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3353 ---- commit 5f6bd3e2fa0567160031cdd067b3e2b1f20c9972 Author: apopov <tank2.alex@...> Date: 2018-01-10T16:08:05Z IGNITE-7191 JDBC: set socket buffer to 64k by default ---- > JDBC: set socket buffer to 64k by default > ----------------------------------------- > > Key: IGNITE-7191 > URL: https://issues.apache.org/jira/browse/IGNITE-7191 > Project: Ignite > Issue Type: Improvement > Components: jdbc > Affects Versions: 2.1 > Reporter: Alexey Popov > Assignee: Alexey Popov > > TCP socket buffer size can significantly affect user-visible performance > (actually, latency) for SQL queries, especially if Ignite cluster is run at > the remote hosts. > It is better to have 64k TCP socket buffer size (instead of default 8k) by > default to avoid possible delays in TCP transport. -- This message was sent by Atlassian JIRA (v6.4.14#64029)