[
https://issues.apache.org/jira/browse/GEODE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-6121.
-------------------------------------
Resolution: Won't Do
Performance measurements with the SnappyData changes show no change or
degradation. I think if we're going to take advantage of this we would need to
take other changes that SnappyData made to the storage model for partitioned
regions, which I'm not prepared to do at this time.
> Port SnappyData DirectChannel comms changes to Geode
> ----------------------------------------------------
>
> Key: GEODE-6121
> URL: https://issues.apache.org/jira/browse/GEODE-6121
> Project: Geode
> Issue Type: New Feature
> Components: membership
> Reporter: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> SnappyData is using an old snapshot of pre-Geode GemFire for one of its data
> stores. They have implemented connection pooling to eliminate the
> connection-explosion problem we have with conserve-sockets=false (which
> pretty much everyone uses). We should port those changes to Geode and
> evaluate their effectiveness.
> https://github.com/SnappyDataInc/snappy-store/commit/49222766a35c99f4853b7b6661457f37b3c39349
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
