4paradigm / 4paradigm/OpenMLDB
improve use of LLJIT
Open
enhancement
execute-engine
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
Current status
- every SQL construct standalone JIT instance, destroyed after single SQL query finished
Better ?
- reuse JIT instance from multiple SQLs
- remove module with ResourceTracker
Contributor guide
Research direction
The issue concerns the LLJIT usage in OpenMLDB's SQL execution. Look for code that creates and destroys JIT instances per query, likely in the SQL execution engine or compiler components. Research how LLJIT instances and ResourceTrackers are currently managed. The goal is to modify the lifecycle to allow reuse across multiple queries, which requires understanding the project's JIT architecture and threading model.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, compilers, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100