graphql-engine/server/benchmarks/benchmark_sets/chinook
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 ci/benchmarks: don't measure decompression in k6 (NOT REAL PERFORMANCE IMPROVEMENT) 2022-09-21 02:07:54 +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

This is the classic chinook data set, which simulates a simple digital media store; with dozen or so tables, some simple relationships, and (depending on the table) a few dozen to a few hundred rows of realistic data per table.

Additionally it has been enriched with some sensible permissions on two new roles: employee, and customer.

Selected for inclusion because it's understandable, standard, familiar and somewhat realistic.