Possibly fix too many open file descriptors - #171
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On my machine, I had troubles starting the application and sometimes other issues, that were not immediately noticable. Looking in the logs, the application crashed because of too many open file descriptors, which primarly were open by matrix-rust-sdk, opening a pool of max(2, 4 * core-count) per sqlite file.
Maintaining now a default of 4 connections (for writing and reading) by using SqliteStoreBuilder directly, this should hopefully improve the performance. This is sadly not really benchmarkable for me in the current state, but evaluating with my same account, I could not notice any regressions and would hope the same for everybody else!
This should be the final solution to #83