Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-3519

Reuse script engine to improve lineage query performance

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.1.0, 2.0.0
    • 2.1.0
    • atlas-core

    Description

      when query lineage info for hive, the throughput reachs only 3 query per second.

      we use jstack and jfr+flame graph tools and found that the  GremlinGroovyScriptEngine object loading class  logic takes much of the time. so we make the GremlinGroovyScriptEngine a global singleton object, which would be shared accross all query threads. finally the query performance improved much and got 200 qps.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            leslizhang zhangxiong
            leslizhang zhangxiong
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h 40m
                1h 40m

                Slack

                  Issue deployment