4paradigm / 4paradigm/OpenMLDB
improve use of LLJIT
- Langage dominant
- C++
- Étoiles
- 1.7k
- Forks
- 331
- Merge moyen
- 12 j 12 h
- PR mergées (30 j)
- 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
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- backend, compilers, performance
- Type d'issue
- Refactorisation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100