database controller watcher event queue optimization
Open
@hzy46 is already working on this.
Since Aug 4, 2020.
pai-dev
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
In database controller, the watcher will send events to write merger. For each framework, the events are in a queue and sent in order. For example, in the following image, there are event 1, 2, 3, 4. Event n will always be sent after event n-1.
Since the transient status is not important, one possible optimization for the event queue is to omit some transient events. e.g. If we have event 1, 2, 3, 4, we can omit event 2 and event 3.
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.
Assessment
This issue has not been assessed yet.