[
https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322232#comment-16322232
]
Alexey Popov commented on IGNITE-7191:
--------------------------------------
Scope of changes:
1. Server side default socket size for thin clients
2. JDBC thin default socket size & tests
3. .Net thin client socket size & tests
PR:
https://github.com/apache/ignite/pull/3353
TC:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests2023Java7&branch_IgniteTests2023Java7=pull%2F3353%2Fhead
> 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)
