Skip to content
This repository has been archived by the owner on Feb 6, 2025. It is now read-only.

Update persistent-caching.md #60

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update persistent-caching.md #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion guides/persistent-caching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ For different use cases there are different types of snapshots:

Timestamping is very fast to capture and compare as it only needs a meta data read from filesystem. Contenthashing is slow compared to that, because it need to read the file content from filesystem. But timestamping might invalidate the cache even when the file content is the same, but only the timestamp changed. This can happen because of multiple factors:

* git operations always update the timestamp. e. g. fresh clone, changing branches
* git operations always update the timestamp. e. g. fresh clone
* save without changes

So the question is: Do you expect timestamp changes, while content stays equal? And is the extra performance cost worth it?
Expand Down