jsonplan: Improve performance for deep objects #30561
Merged
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.
When calculating the unknown values for JSON plan output, we would previously recursively call the
unknownAsBool
function on the current sub-tree twice, if any values were unknown. This was wasteful, but not noticeable for normal Terraform resource shapes.However for deeper nested object values, such as Kubernetes manifests, this was a severe performance problem, causing
terraform show -json
to take several hours to render a plan.This commit reuses the already calculated unknown value for the subtree, and adds benchmark coverage to demonstrate the improvement.
Fixes #30548.
Benchmark results
For these benchmarks, we construct a fairly narrow object value of variable depth, then compute its unknown value. The execution time difference for this change is:
Before:
After: