hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-16 09:51:59 +03:00
Code Issues Projects Releases Wiki Activity
2467e23ef6
graphql-engine/server/benchmarks/benchmark_sets/huge_schema
History
Brandon Simmons 167e8f4cae server/benchmarks: configurable pause after each adhoc benchmark, bef… 
…ore checking allocations

It seems like there might be some non-determinism exposed after #10206 we see a huge regression reported in live_bytes in huge_schema which apparently disappears, later reappearing in
https://github.com/hasura/graphql-engine-mono/pull/10226#issuecomment-1697897108

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10240
GitOrigin-RevId: 8e9533cb9fd7db6c002f00d1d9cb0331d574d6a2
2023-08-30 20:27:53 +00:00
..
adhoc_operations server/benchmarks: configurable pause after each adhoc benchmark, bef… 2023-08-30 20:27:53 +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

README.md

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.