You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2016/07/28 09:27:20 UTC

[jira] [Updated] (IGNITE-3220) I/O bottleneck on server/client cluster configuration

     [ https://issues.apache.org/jira/browse/IGNITE-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yakov Zhdanov updated IGNITE-3220:
----------------------------------
    Labels: performance  (was: )

> I/O bottleneck on server/client cluster configuration
> -----------------------------------------------------
>
>                 Key: IGNITE-3220
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3220
>             Project: Ignite
>          Issue Type: Bug
>          Components: clients
>            Reporter: Alexei Scherbakov
>            Assignee: Yakov Zhdanov
>            Priority: Critical
>              Labels: performance
>             Fix For: 1.7
>
>
> Where is an I/O bottleneck if a client tries to perform many
> transactions involving puts and gets in a highly concurrent manner using socket transport to a single server node deployed on powerful multicore computer.
> In what case throughput dramatically decreases (up to 30 times in comparison with running test in single JVM) because everything is delayed by server I/O thread.
> Current workaround for such scenario is using more clients (or servers).
> We should add configuration parameter such maxConnectionsPerClient, allowing client to connect to server using several simultaneous connections decreasing I/O bottleneck.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)