WIP: Optimize run_sql by avoiding cloning immutable data #1110
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.
STATUS: DRAFT / WORK IN PROGRESS - Does not compile yet
This PR refactors the request handling to separate immutable request data from mutable execution state, avoiding unnecessary cloning of potentially large data structures.
Problem
Currently,
run_sql()clones the entireRequestInfowhich includes:This is wasteful since only
set_variablesandclone_depthneed to be cloned.Solution
Split into two structures:
RequestInfo: immutable request data (wrapped inRc)ExecutionContext: mutable execution state + reference to RequestInfoBenefits
run_sql()callsStatus
Based on: #1109