[db] Trace DB performance improvement
Open
@nasahlpa is already working on this.
Since Jan 15, 2024.
Priority:P2
- Dominant language
- Jupyter Notebook
- Stars
- 43
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When using the new OT trace database in a multi-processing setting (e.g., CECA.py), the new DB is slower than the older CW DB. The reason for that is how the database connection with SQLAlchemy is established. Instead of opening a new connection each time, we should keep the connection open and allow different Ray workers accessing them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.