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
we have some GQL queries that produce fairly large results of several MB.
I noticed that most of the actual response text is whitespace formatting of the JSON. While all of that is compressed with Gzip, it will still increase total processing time as the white space has to be processed at least 4 times (json generation, compression, decompression, json parsing).
I also noticed that the initial json result from Postgresql does not contain any whitespace. So Hasura must add that before forwarding to the client.
Is there a way to disable adding this whitespace, or even disable mutating the Postgresql response at all?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
we have some GQL queries that produce fairly large results of several MB.
I noticed that most of the actual response text is whitespace formatting of the JSON. While all of that is compressed with Gzip, it will still increase total processing time as the white space has to be processed at least 4 times (json generation, compression, decompression, json parsing).
I also noticed that the initial json result from Postgresql does not contain any whitespace. So Hasura must add that before forwarding to the client.
Is there a way to disable adding this whitespace, or even disable mutating the Postgresql response at all?
Beta Was this translation helpful? Give feedback.
All reactions