having said that, if you are using v9 or v8 try la...
# graphql-kotlin
s
having said that, if you are using v9 or v8 try latest versions, we found a very bad memory leak with property data fetchers being instantiated by property by graphql operation, so we are using a singleton now, more info in release notes.
👍 1
a
I have a similar issue related to the memory and data fetchers; our servers require more than 8GB of memory, only for the startup introspection and data fetchers creation in memory. Can you help us? How does your singleton fix this?