graphql-engine/server/benchmarks/benchmark_sets/huge_schema
Brandon Simmons 7066b52777 dev.sh: support graphql-engine-pro
So you can do:

```
$ HASURA_GRAPHQL_EE_LICENSE_KEY=... scripts/dev.sh graphql-engine-pro
```

along with the `--prof-*` modes etc.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/8894
GitOrigin-RevId: 2257749b2936cbd3230beb23e774ac92989e2fbc
2023-04-25 10:54:30 +00:00
..
adhoc_operations ci: sleep 3 seconds after allowlist adhoc operation benchmark 2023-04-24 18:02:30 +00:00
config.query.yaml dev.sh: support graphql-engine-pro 2023-04-25 10:54:30 +00:00
dump.sql.gz Add initial benchmark suite, running in CI (closes hasura/graphql-engine-mono#736) 2021-07-08 18:19:51 +00:00
README.md Add initial benchmark suite, running in CI (closes hasura/graphql-engine-mono#736) 2021-07-08 18:19:51 +00:00
replace_metadata.json Add initial benchmark suite, running in CI (closes hasura/graphql-engine-mono#736) 2021-07-08 18:19:51 +00:00

Huge Schema is an anonymized version of a real schema, without row data. It is notable for:

  • having hundreds of tables, and relationships (including cycles)
  • dozens of different roles and permissions

We select it for inclusion because the memory requirements to serve such a large schema are currently high.

We also test a small and a big query (returning no data) to see if schema size affects latency and (for the latter case) to time SQL generation.