Conversation
Member
|
We should look into memory consumption as an effect of using |
Contributor
Author
|
Closing, figuring out the memory thing would be require a set of benchmarks and a system to measure, which we don't have and I can't built it right now. |
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
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.
Fuzzing is slow because regex is taking ~28 of total(!) time. Yes, you heard that right. That includes generation, compilation, deployment ,running ,and comparing the logs/state/returndata.
It adds
static,const, andstd::regex::optimize.Perf of fuzzing before:
Perf of fuzzing after:
optimize() is now 48 instead of 41% of total runtime. No idea how this affects normal compilation. But I'd guess it should help there too?