Brandon Simmons fc9cc14943 ci/benchmarks: don't measure decompression in k6 (NOT REAL PERFORMANCE IMPROVEMENT) ... 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		2022-09-21 02:07:54 +00:00
..
graphql_server	bump python test suite dependencies	2022-01-17 07:40:56 +00:00
cleanup.sh	Remote Schema Customization take 2 using parser tranformations	2021-07-30 11:33:59 +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
replace_metadata.json	Remote Schema Customization take 2 using parser tranformations	2021-07-30 11:33:59 +00:00
setup.sh	Remote Schema Customization take 2 using parser tranformations	2021-07-30 11:33:59 +00:00
SKIP_CI	benchmarks: skip failing remote_schema suite	2021-11-17 13:00:45 +00:00
SKIP_PR_REPORT	Jberryman/1993 skip just report mode	2021-08-06 18:41:27 +00:00