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

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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Done
    • 3.4.7
    • 3.5.0, 3.4.9
    • driver
    • None
    • 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

            spmallette Stephen Mallette
            gfxman Kelvin R. Lawrence
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: