-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance got degraded after upgrade from 1.5.7 version to 1.5.8 for the SAXScanner. #39
Comments
I think we need @davidbarbrowatwork to review your requested change because I believe it was his changes to 1.5.8 that affected the code you are trying to fix. Can you try to find/nudge him to get him to review/approve your requested change? |
Hi @davidbarbrowatwork, I found the performance is down by almost 50% in the 1.5.8 antisamy version comapre to 1.5.7. |
Hi @davewichers , can you please try to connect to @davidbarbrowatwork to review this PR, as I couldn't get any response from. |
I tried as well, but I can try again. You can find him and try on Twitter.
Dave
… On Feb 4, 2020, at 1:58 AM, Dharmendra Kumar ***@***.***> wrote:
Hi @davewichers , can you please try to connect to @davidbarbrowatwork to review this PR, as I couldn't get any response from.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi @davewichers, if you have twitter id of @davidbarbrowatwork can you please share. Thanks |
I think it is @ dbarbrow. |
Hi @davewichers, |
This is the 1.5.8 release: https://github.com/nahsra/antisamy/releases and I believe there is a checkin tag for that release. |
Hi @davewichers, Change that i have made was present in the branches below 1.5.8. For example
And I got an instruction to use 1.5.8 version of the Antisamy.So I request to please consider it for version 1.5.8. |
…ing prep for 1.5.8 release to address issue #39. Upgrade a few components in pom that have been released since 1.5.8 release. This should be the 1.5.9 release.
The requested line has been added, and this fix was just released in version v1.5.9 of AntiSamy, along with a few dependency upgrades. |
After upgrading antisamy jar version from 1.5.7 to 1.5.8 performance got down by 40-50%.
After comparing the 1.5.8 version of code with the 1.5.7. I found that in case of SAXScanner, in the class AntiSamySAXScanner after doing all the scanning process the cached item is not being added to the cachedItems Queue, because of which for every scan call object of CachedItem class is being created.
And this create operation for every scan is lowering down the performance.
The text was updated successfully, but these errors were encountered: