Changing default of syncDbAfterWrite to True #1968
Merged
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.
What is the change?
syncDbAfterWrite
now defaults toTrue
.Why is the change being made?
This setting enables the database to be written to the working directory each time the database interface has an interaction. This basically ensures that a relatively current database is written if a job fails in a way that prevents going through
interactError
. There is potential overhead in the operation due to the file I/O. But I checked with a large model, where the runtime difference would be greatest, and it didn't have any noticeable impact on runtime.Checklist
doc
folder.pyproject.toml
.