Speed up historical forecast parsing by avoiding pd.json_normalize#38
Merged
sam-watttime merged 1 commit intofuture-releasefrom Mar 12, 2025
Merged
Speed up historical forecast parsing by avoiding pd.json_normalize#38sam-watttime merged 1 commit intofuture-releasefrom
sam-watttime merged 1 commit intofuture-releasefrom
Conversation
jcofield
pushed a commit
that referenced
this pull request
Mar 14, 2025
jcofield
pushed a commit
that referenced
this pull request
Mar 15, 2025
jcofield
pushed a commit
that referenced
this pull request
Nov 2, 2025
jcofield
pushed a commit
that referenced
this pull request
Nov 2, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
pd.json_normalizeis not efficient to use in a loop. When profiling code, calls to_parse_historical_forecast_jsonimproved from 10.8s -> 0.38s for 1% of 1 year of forecasts.