Try to initialize xmlXPathContext faster #3388
Closed
+176
−150
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 problem is this PR intended to solve?
A variation on solving the "slow xpath context creation" problem described in #3266. See first attempt at #3378.
Copying the struct and the hash tables is slightly faster than calling
xmlXpathNewContext
:But still slower than re-using the context object ("edge", v1.18.0.rc1):
I probably won't merge this, but thought it was worth sharing for posterity.
Next I'm going to try an extension of #3378 that will push and pop "eval frames" that include the internal state but also the registered functions/namespaces/lookup handlers.