You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/03/02 14:28:00 UTC

[jira] [Updated] (TINKERPOP-1774) Gremlin .NET: Support min and max sizes in Connection pool

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

stephen mallette updated TINKERPOP-1774:
----------------------------------------
    Affects Version/s: 3.2.7

> Gremlin .NET: Support min and max sizes in Connection pool
> ----------------------------------------------------------
>
>                 Key: TINKERPOP-1774
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1774
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: dotnet
>    Affects Versions: 3.2.7
>            Reporter: Jorge Bay
>            Priority: Minor
>
> Similar to the java connection pool, we should limit the maximum amount of connections and start with a minimum number.
> It would also a good opportunity to remove the synchronous acquisitions of {{lock}} in the pool implementation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)