You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2016/11/14 20:11:59 UTC
[jira] [Assigned] (OAK-5106) Reuse NioEventLoopGroup in standby
client
[ https://issues.apache.org/jira/browse/OAK-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothee Maret reassigned OAK-5106:
-----------------------------------
Assignee: Timothee Maret
> Reuse NioEventLoopGroup in standby client
> -----------------------------------------
>
> Key: OAK-5106
> URL: https://issues.apache.org/jira/browse/OAK-5106
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Affects Versions: 1.5.13
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Fix For: 1.5.14
>
>
> The Standby client code does instantiate a new {{NioEventLoopGroup}} for every cycle (5 seconds). The standby tests do instantiate many {{NioEventLoopGroup}}.
> Although {{NioEventLoopGroup}} are closed properly, each of them consume files and management overhead (seting up/down). An improvement would be to reuse the {{NioEventLoopGroup}} in standby client across polling cycles and reuse {{NioEventLoopGroup}} in the test code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)