You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/11 15:40:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16717398#comment-16717398 ] 

ASF GitHub Bot commented on TINKERPOP-1774:
-------------------------------------------

FlorianHockmann closed pull request #903: Gremlin.Net: Add ConnectionPool min and max sizes TINKERPOP-1774
URL: https://github.com/apache/tinkerpop/pull/903
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Assignee: Florian Hockmann
>            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)