[ATLAS-3519] Reuse script engine to improve lineage query performance

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.0, 2.0.0
• Fix Version/s: 2.1.0
• Component/s: atlas-core
• Labels: lineage performance
• Assignee: zhangxiong
• Reporter: zhangxiong
• Created: 08/Nov/19 10:58
• Updated: 09/Oct/22 03:41
• Resolved: 21/Nov/19 19:45

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.

Issue Links

• links to: code review
• links to: GitHub Pull Request #75