Improve performance by throttling database change events #5843
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now database change events trigger the following actions a bit delayed, which leads to a smooth user experience when working in the entry editor:
Should also fix #5734. At least opening a very big bib file in the 3.8.2 file version, leads to 30 sec of high CPU and 2 gb ram consumption. After this period, CPU goes down to almost 0 and ram also to about 1gb, which seems reasonable.