Graphql Engine V3 metadata.json max size

[varnaik]

Hello,

I am using the hasura graphql engine v3 with postgres dataconnector . I have a metadata.json as huge as 130MB in size and over 3Million lines of json. I see that the graphql engine runs out out memory even at 90GB without any logs.

1. Is this expected ?
2. Is there a limit on the size of the metadata.json file that can be used with the v3 engine (Causing no/few ms extra latency)?
   I am working with a database with over 800 Tables and each table with around 100 fields on average.

PS: These environment variables are configured for extra logging already on the engine

        - name: EXPOSE_INTERNAL_ERRORS
          value: "true"
        - name: EXPORT_TRACES_STDOUT
          value: "true"

[robertjdominguez]

Hi, @varnaik — thanks for raising this. I'm tagging some folks internally that can give you some guidance.

[varnaik]

Hi @robertjdominguez ,
Any update on this ?

[robertjdominguez]

Good timing as I was just navigating here to reply as I signed on this AM 😅

From what's been passed down, the metadata-build service is capable of handling request payloads up to 100 MB. The best advice I can pass on currently is to determine which models and commands are unnecessary and to remove them (i.e., ddn model remove <model_name> or ddn command remove <command_name>).

In the event all 800 tables and insert, update, and delete operations are needed on all of them, we can troubleshoot further.