kodiakhq[bot] 4d86cd3a62 Fix #9447 bad memory usage ... A fix for #9447 Before this change, for the workload in the ticket, we saw a memory stay at around 4 GB an hour after the workload ended. after this change we see both a lower memory high watermark, and also see memory come back to baseline at the end as we expect (after the `HASURA_GRAPHQL_PG_CONN_LIFETIME` and a subsequent `_idleStaleReaperThread` interval elapses). But note the numbers given on any given machine may be slightly different, since the behavior depends on the version of glibc and processor speed (Since the test case depends on the server being overloaded). This might also help some users commenting in https://github.com/hasura/graphql-engine/issues/9592 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/9823 GitOrigin-RevId: 5650aa42d10d46c418c21686983a982d69011884		2023-07-25 11:24:57 +00:00
..
9447_repro	Fix #9447 bad memory usage	2023-07-25 11:24:57 +00:00
chinook	ci/benchmarks: don't measure decompression in k6 (NOT REAL PERFORMANCE IMPROVEMENT)	2022-09-21 02:07:54 +00:00
chinook_throughput	server/benchmarks: remove introspection from throughput benchmarks	2023-05-11 17:50:03 +00:00
deep_schema	Add benchmarks for allowlist operations	2022-11-01 17:28:15 +00:00
huge_schema	dev.sh: support graphql-engine-pro	2023-04-25 10:54:30 +00:00
remote_schema	dev.sh: support graphql-engine-pro	2023-04-25 10:54:30 +00:00