[
https://issues.apache.org/jira/browse/GEODE-6576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857906#comment-16857906
]
ASF subversion and git services commented on GEODE-6576:
--------------------------------------------------------
Commit 5210670ca891729da78ead36dc1b63f49eced653 in geode-native's branch
refs/heads/develop from mivanac
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5210670 ]
GEODE-6576: Improvements in cleanStaleConnections method (#477)
Improvements in cleanStaleConnections method:
- introduce phasing
- return connections to pool as soon as possible
This fault can be reproduced with geode-native-examples - putgetremove. For
reproduction test:
- set min and max connections to 800.
- set LoadConditioningInterval to 60 secs
- run continues get operation, and measure duration of get operation.
- Every 60 seconds you will see peaks with time duration over 100ms.And this is
the problem.
> DB connection rebalancing improvement
> -------------------------------------
>
> Key: GEODE-6576
> URL: https://issues.apache.org/jira/browse/GEODE-6576
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
> Labels: needs-review, pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When using min=max=120 connections, and about 2000 TPS it is observed, that
> every 5 minutes (load-conditioning-interval) we get significant delays . But
> I suspect you could reproduce it at any configuration, if you look for
> increased delays when driver rebalances connections
> (load-conditioning-interval).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
