Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2397

Don't create the default Gyro serializer if the caller specifies a different one

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 3.4.7
    • Fix Version/s: 3.5.0, 3.4.9
    • Component/s: driver
    • Labels:
      None
    • Environment:
      Gremlin Java client at the 3.4.7 level running on Linux using AWS Lambda and also measured using a generic Linux machine.

      Description

      In serverless environments such as AWS Lambda, the startup time of the Gremlin client becomes important. This is especially so when the serverless container is "cold".  I have been getting fairly regular end user feedback on this so we started doing some analysis. There are many contributing factors but one thing that we could (and I think should) fix is the fact that the Gremlin Java client always creates a Gyro (default) serializer even if a different one such as GraphBinary is specified. To create the unused Gyro serializer adds almost a full second to the cold start time for the Gremlin client on a typical serverless container host.

        Attachments

          Activity

            People

            • Assignee:
              spmallette Stephen Mallette
              Reporter:
              gfxman Kelvin R. Lawrence

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment