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.
Related issue(s)
Resolves #791
Description
Optimizes the
expression_with_precedence
parser which was the main cause of performance lost in the frontend.The command used for testing was
nargo prove p
on the source projectTiming details are averages of 10 runs and the results are as follows:
So it is roughly a 5x speedup in debug and a 2.9x speedup on release.
For a more detailed flamegraph, see the graphs uploaded in #791.
Summary of changes
The old
expression_with_precedence
parser recursively called itself for each precedence level, but also called each child level twice when constructingexpr <op> expr
, leading to an exponential blowup. Note though that this is from the time it takes to construct the parser before running it, so this was a large fixed cost rather than one that scaled with program size. This PR simply adds a.clone()
to reuse the first parser and make this function linear rather than exponential in time.Checklist
cargo fmt
with default settings.