You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PropertyDataFetcher::findPubliclyAccessibleMethod which calls Class::getMethod is one of the more expensive methods performance-wise I found when profiling a GraphQL API example project.
Perhaps there should be some caching of method handles?
I guess graphql-java-tools uses reflectasm to make this better, but since graphql-java-tools lags behind in compatbility with dataloaders etc, I would prefer to only depend on graphql-java (and graphql-java-tools seems to have other performance issues...)
Activity
rrva commentedon Apr 5, 2018
I guess graphql-java-tools uses reflectasm to make this better, but since graphql-java-tools lags behind in compatbility with dataloaders etc, I would prefer to only depend on graphql-java (and graphql-java-tools seems to have other performance issues...)
rrva commentedon May 11, 2018
@bbakerman Thanks for fixing this!