Skip to content
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

Fix performance issues #241

Merged
merged 18 commits into from
Dec 5, 2023
Merged

Fix performance issues #241

merged 18 commits into from
Dec 5, 2023

Conversation

nck-mlcnv
Copy link
Contributor

During a test of the new iguana version, I noticed that there were some severe performance issues during the processing of the results, after the stresstest has finished. The biggest issue of it was the jena library and the canonical method inside its XSDDuration class, which didn't support nanoseconds as decimal digits for the durations.
This PR aims to circumvent this issue by creating our own LiteralType class, which might not be the best solution.

I've also made the QuerySource cache its hashCode, which also caused some performance issues, as the hashCode is needed everytime the id of a Query from a QueryHandler is retrieved. Caching the QuerySource hashCode shouldn't be a problem though, as we don't expect the hashCode to change itself during the benchmark.

@nck-mlcnv nck-mlcnv requested a review from bigerl November 28, 2023 11:21
@nck-mlcnv nck-mlcnv requested a review from mcb5637 November 28, 2023 12:15
Copy link
Member

@bigerl bigerl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just some little things.

Copy link

@mcb5637 mcb5637 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as i can tell the spec of java.time.Duration matches xsd:dayTimeDuration and not xsd:duration.
(Except if the duration is >= 24 hours. Then java still outputs durations where it should output days. But the representation is still valid and should be accepted on parsing.)

@nck-mlcnv nck-mlcnv merged commit fdbffa4 into develop Dec 5, 2023
2 checks passed
@nck-mlcnv nck-mlcnv deleted the fix/performance-issue branch December 5, 2023 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants