[jira] [Closed] (TINKERPOP-2445) Speed up client initialization

["Divij Vaidya (Jira)" <ji...@apache.org>]

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

Divij Vaidya closed TINKERPOP-2445.
-----------------------------------
    Fix Version/s: 3.4.9
                   3.5.0
         Assignee: Divij Vaidya
       Resolution: Fixed

> Speed up client initialization
> ------------------------------
>
>                 Key: TINKERPOP-2445
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2445
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.5.0, 3.4.8
>            Reporter: Divij Vaidya
>            Assignee: Divij Vaidya
>            Priority: Minor
>              Labels: breaking
>             Fix For: 3.5.0, 3.4.9
>
>         Attachments: screenshot-1.png
>
>
> The current Java client has a lot of initialization overhead. Some of the things we could do to trim the fat are:
> 1. Parallelize the connection creation inside a connection pool, i.e. make [this for loop|https://github.com/apache/tinkerpop/blob/3.4-dev/gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/ConnectionPool.java] parallel. 
>  2. Do not create a bootstrap [for every connection|https://github.com/apache/tinkerpop/blob/3.4-dev/gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Connection.java#L111]. A single bootstrap could be reused.
> 3. Remove SASL Handler from the pipeline after negotiation is complete for a connection.
> 4. Do not initialize SASL Handler if not required.
> As part of this task, we should profile the start-up time and identify other places where we could optimize the start-up time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)