Cache processed activities #42
Merged
Conversation
This file contains 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
hugovk
force-pushed
the
cache-processed-activities
branch
from
e99c44c to
0e705cd
Compare
|
Fantastic! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This speeds up the "Processing data..." step by caching the generated Pandas dataframe as a pickle file on disk.
For example, with an 8-core Mac, processing all my 3,699 GPX files takes 34s on first pass and creates a 305 MB cache file on disk (the GPX files are 822 MB). For the second run, it takes less than 2s to load the cache file.
For 580 GPX files from 2023, it takes 4s on first pass to create a 50 MB file.
Also add some type hints.