OverlappingFieldsCanBeMerged is slow
See original GitHub issueOverlappingFieldsCanBeMerged
can be very slow when many fragments in the query.
Scala implementation resolved it by optimizing the algorithm.
See https://github.com/sangria-graphql-org/sangria/pull/12.
Can we do something similar in graphql-java?
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (6 by maintainers)
Top Results From Across the Web
sangria-graphql/sangria - Gitter
Regarding OverlappingFieldsCanBeMerged . I think it's fair to say that this is the most complex validation of them all :) So it does...
Read more >Readme — graphql-clj-awol 0.1.21-SNAPSHOT - cljdoc
[ ] Overlapping fields can be merged (https://github.com/graphql/graphql-js/blob/master/src/validation/rules/OverlappingFieldsCanBeMerged.js).
Read more >Extremely slow GraphQL performance even with very simple ...
I am trying to switch over from REST to GraphQL, and am experiencing horribly slow responses for queries. As in 5000-7000+ ms for...
Read more >Lisenser - Ubisoft Connect
`.mont()` is generally faster than `.red(num)`, but slower than ... by default in all envs*) - `NoUnusedVariables` - `OverlappingFieldsCanBeMerged` ...
Read more >databases/arangodb32: Distributed NoSQL ... - FreshPorts
... our listservers still use it - www/chromium, solely because of popular demand, upstream is (slowly) working on porting it to Python 3 ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
hi,
we are planning to address this issue via https://github.com/graphql-java/graphql-java/pull/2495
Special thanks to @redhead: we really appreciate the effort you put in, but ultimately we could not accept a scala version of the algorithm from a longterm maintainability POV. But we implemented the same algorithm based on the xing article.
We are planning to replace the current validation completely with the more performant one.
Andi
merged now and will be part of 17.0