Replaced template name collision detection algorithm with a hash table #1
Conversation
This file contains 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
added 2 commits
August 20, 2015 18:57
…e look up. For big XSLTs (>50000 templates) this results in a huge improvement of the compilation time.
…ddTemplate and store now the xsltTemplatePtr inside instead of the previous xmlNodePtr. xsltFindTemplate is now using this hash table for template look up instead of linear search.
gnomesysadmins
pushed a commit
that referenced
this pull request
Sep 14, 2015
For big XSLTs (>50000 templates) this results in a huge improvement of the compilation time. Thanks to Christian Ceelen for the original patch. Fixes GitHub pull request #1
aasselin-en
added a commit
to euronext/libxslt
that referenced
this pull request
Mar 13, 2020
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.
Replaced template name collision detection algorithm with a hash table look up. For big XSLTs (10000+ templates) this results in a huge improvement of the compilation time (~factor 20).
I tried to follow the style and use sensible locations for the new code. Please let me know if i got something wrong.