Database controller performance optimization candidate items
Open
Nobody has claimed this yet.
pai-dev
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
- Merge updates in event queue https://github.com/microsoft/pai/issues/4780
- Merge watcher and write-merger into one process to avoid (De)Serialization overheads.
- Instead of write DB every time, can we first compare the result with oldFramework, if they are deep equal, skip this DB write.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the database controller areas covering the event queue, watcher, write-merger, and oldFramework comparison, along with issue #4780. Clarify which optimization is in scope and define done through measurable reductions in serialization overhead and unnecessary database writes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100