You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/25 19:36:39 UTC
[jira] [Commented] (IGNITE-2329) Get rid of Iterator for selected
keys in NIO server
[ https://issues.apache.org/jira/browse/IGNITE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115719#comment-15115719 ]
ASF GitHub Bot commented on IGNITE-2329:
----------------------------------------
GitHub user yzhdanov opened a pull request:
https://github.com/apache/ignite/pull/422
fixed https://issues.apache.org/jira/browse/IGNITE-2329 + forceKeysFu…
fixed https://issues.apache.org/jira/browse/IGNITE-2329 + forceKeysFu…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yzhdanov/ignite ignite-gc-opts
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/422.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 #422
----
commit 914b365f79311e56c46ee4e214f60d60753030cc
Author: Yakov Zhdanov <yz...@gridgain.com>
Date: 2016-01-25T18:34:43Z
fixed https://issues.apache.org/jira/browse/IGNITE-2329 + forceKeysFuture opts
----
> Get rid of Iterator for selected keys in NIO server
> ---------------------------------------------------
>
> Key: IGNITE-2329
> URL: https://issues.apache.org/jira/browse/IGNITE-2329
> Project: Ignite
> Issue Type: Sub-task
> Components: general
> Reporter: Alexey Goncharuk
> Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> Every time a NIO thread wakes up on selected keys, a new iterator is created since selector returns a Set.
> There is a technique that makes it possible to avoid new iterator creation, that is implemented in Netty.
> For details, see io.netty.channel.nio.NioEventLoop and processSelectedKeysOptimized method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)