hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-16 01:44:03 +03:00
Code Issues Projects Releases Wiki Activity
73b161b2bc
graphql-engine/server/benchmarks/benchmark_sets/huge_schema
History
Brandon Simmons a3fc1889bb benchmarks: add an initial adhoc operation mode, suitable for benchma… 
…rking metadata operations

And add an initial benchmark for replace_metadata, to unblock some
performance improvements to that op in a PR to be merged after this.

This is an MVP just to have something in CI to reference when optimizing
metadata operations. See TODO for roadmap.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3673
Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com>
GitOrigin-RevId: 968d1f92ca79c78ad90b2304d2214069bc739621
2022-02-22 16:59:44 +00:00
..
adhoc_operations benchmarks: add an initial adhoc operation mode, suitable for benchma… 2022-02-22 16:59:44 +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.