Improve CucumberExpression creation performance #189
Closed
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.
🤔 What's changed?
I rewrote a regular expression to improve
CucumberExpression
creation performance.⚡️ What's your motivation?
My motivation is to have a better performance for the Cucumber framework.
I made a benchmark with JMH which shows that the modified method is about 15% faster (see escapeRegex2 below) :
Benchmark Mode Cnt Score Error Units
CucumberExpressionBenchmark.escapeRegex0 thrpt 25 726563,091 ± 15558,020 ops/s
CucumberExpressionBenchmark.escapeRegex2 thrpt 25 833512,235 ± 25088,968 ops/s
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
Nothing.
📋 Checklist: