perf: CoreStatement uses optimize regex for generated key matches #1080
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.
While profiling some software that makes heavy use of prepared statements and SQLite, I noticed that each call to
java.sql.Connection#prepareStatement(java.lang.String)
ended up compiling a regex pattern as part oforg.sqlite.core.CoreStatement.<init>(SQLiteConnection)
construction. This appears to be a recent addition as part of #1056 with example call trace showing up as over 75% of total allocations in JFR:Because JDK
Pattern
instances are immutable and thread-safe, we can compile the regex onCoreStatement
class load to a static field for reuse, and adjust the regex to avoid additional possible allocations from trimming and converting the SQL to lower case, as well as use non-capturing groups to avoidPattern#matcher
allocating theint[]
arrays associated with capture groups.