hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 01:12:56 +03:00
Code Issues Projects Releases Wiki Activity
2e1be1d2c5
graphql-engine/server/benchmarks/benchmark_sets/huge_schema
History
Brandon Simmons c415cd7c0d server benchmarks: add introspection queries 
This excercises a different code path from regular queries and is
pretty slow. Motivated by https://github.com/hasura/graphql-engine-mono/pull/2835

We may need to break chinook up into two sets if it keeps growing or
becomes a bottleneck, but do that later.

GitOrigin-RevId: 5832aef520db85f694924e038c0f2c9a7dd17a13
2021-12-09 15:10:42 +00:00
..
config.query.yaml server benchmarks: add introspection queries 2021-12-09 15:10:42 +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.