[
https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332465#comment-16332465
]
Alexey Popov commented on IGNITE-7191:
--------------------------------------
[~ptupitsyn] , I run some benchmarks and check wireshark logs with different
socket size options.
0 (default) works as ~ 256k with a good network at Win client and Linux server.
So, it seems that this improvement is not required for modern OSs.
I will double check the results later.
> 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
> Priority: Major
> Fix For: 2.5
>
>
> 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
(v7.6.3#76005)
