Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: remove note on disk space for caching #5534

Merged
merged 5 commits into from
May 24, 2022
Merged

docs: remove note on disk space for caching #5534

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
aa49af3
docs: remove note on disk space for caching
ltalirz May 23, 2022
e87ac76
incorporate feedback from code review
ltalirz May 23, 2022
b86a721
incorporate suggestions from code review
ltalirz May 23, 2022
906e60b
Update docs/source/topics/provenance/caching.rst
ltalirz May 24, 2022
13c9b55
Merge branch 'main' into docs-caching
ltalirz May 24, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/source/topics/provenance/caching.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,9 @@ Limitations and Guidelines
While AiiDA's hashes include the version of the Python package containing the calculation/data classes, it cannot detect cases where the underlying Python code was changed without increasing the version number.
Another scenario that can lead to an erroneous cache hit is if the parser and calculation are not implemented as part of the same Python package, because the calculation nodes store only the name, but not the version of the used parser.

#. Note that while caching saves unnecessary computations, it does not save disk space: the output nodes of the cached calculation are full copies of the original outputs.
#. While caching saves unnecessary computations, it does lead result in duplication of the cached calculation and its output nodes in the provenance graph.
At the same time, AiiDA's default disk-objectstore storage backend comes with automatic de-duplication at the object level.
ltalirz marked this conversation as resolved.
Show resolved Hide resolved
Disk usage therefore remains unaffected with this backend, except for node metadata stored at the database level.

#. Finally, When modifying the hashing/caching behaviour of your classes, keep in mind that cache matches can go wrong in two ways:

Expand Down