mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-15 17:31:56 +03:00
fc9cc14943
See: https://github.com/grafana/k6/issues/2685 It might be interesting to think about taking into consideration decompression time when thinking about performance, but In general I think doing so is surprising and I wasted a lot of time trying to figure out why my optimizations to the compression codepath weren't improving things to the degree I expected The downside here is we lose error reporting, so you'll need to only set discardResponseBodies: true after the query has been tested. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5940 GitOrigin-RevId: 82a589a59b93f10ffb5391e4a3190459fb6e613b |
||
|---|---|---|
| .. | ||
| adhoc_operations | ||
| config.query.yaml | ||
| dump.sql.gz | ||
| README.md | ||
| replace_metadata.json | ||
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.