Tirumarai Selvan

@cheets @tjenkinson Hey folks, just to confirm once again. You had the exact same metadata in previous versions and it didn't cause a memory growth like in newer versions?

@cheets We are unable to reproduce this on idle schema like you mentioned here: https://github.com/hasura/graphql-engine/issues/9592#issuecomment-1551596064 You are saying you can't reproduce this on AKS. Do you want to test with...

@NikPaushkin @tjenkinson Do you see some kind of leak with no traffic as well?

@tjenkinson Do you also have remote schema permissions?

@tjenkinson Is it possible for you to send us your metadata? You can email me at `[email protected]`.

@tjenkinson You can send us a smaller version by redacting or removing any sensitive info (it need not even work)? This is just to short circuit lots of metadata related...

@dostalradim Are you able to share your metadata with us? You can email it to me at `[email protected]` (feel free to remove any sensitive info)

@dostalradim This is very helpful. Thank you. Could you also help us with the kind of activity that you have on this deployment? Is it queries, mutations, subscriptions, metadata related?

@dostalradim Thank you...this really helps. We are working on this.

I solved this issue with ``` def call(env) @streaming = true super end def rewrite_response(triplet) status, headers, body = triplet headers.delete "transfer-encoding" triplet end ```