audb.load_to() use cache for tables #221
Draft
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.
Closes #220
This loads missing tables from the cache to the build folder.
In addition, we avoid storing the tables an additional time to the
db_root
folder.It stores the tables in the cache under the version number as given by the dependency table,
this avoids caching the same table again for each version, but this is not something that is already integrated in
audb.load_table()
.Execution time
I measured execution time by running
for a large database (salamander-a) with lots of tables.
What is not ideal yet, is that by using
audb.load_table()
to load single tables we block the processes when several tables need to be stored in the same cache folder.So maybe we should target a general refactoring of the table storing code.