Skip to content

Optimize GraphQLUnionType.isPossibleType #3798

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

Merged

Conversation

kilink
Copy link
Contributor

@kilink kilink commented Jan 23, 2025

Remove the allocation overhead of the stream / lambda in isPossibleType; don't have the flame graph on hand any longer unfortunately but this was showing up as an allocation hotspot for one of our apps.

@dondonz
Copy link
Member

dondonz commented Jan 23, 2025

I am probably the cause of the failing builds, PR coming soon! Thanks for the PRs

@dondonz
Copy link
Member

dondonz commented Jan 23, 2025

I reverted my PR that caused the problem, please update from master and your builds should be green again

Remove the allocation overhead of the stream / lambda in isPossibleType.
@kilink kilink force-pushed the graphql-union-type-stream-overhead branch from 60d5a0a to 103a54c Compare January 24, 2025 00:12
@dondonz dondonz added the performance work that is primarily targeted as performance improvements label Jan 25, 2025
@dondonz dondonz added this to the 23.x breaking changes milestone Jan 25, 2025
Copy link
Member

@bbakerman bbakerman left a comment

Choose a reason for hiding this comment

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

Thanks for this

@bbakerman bbakerman merged commit f93b062 into graphql-java:master Jan 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance work that is primarily targeted as performance improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants