Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ingest benchmark: after effective_io_concurrency = 100 we can increas…
…e compute side parallelism (#9904) ## Problem ingest benchmark tests project migration to Neon involving steps - COPY relation data - create indexes - create constraints Previously we used only 4 copy jobs, 4 create index jobs and 7 maintenance workers. After increasing effective_io_concurrency on compute we see that we can sustain more parallelism in the ingest bench ## Summary of changes Increase copy jobs to 8, create index jobs to 8 and maintenance workers to 16
- Loading branch information
277c33b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6941 tests run: 6631 passed, 2 failed, 308 skipped (full report)
Failures on Postgres 17
test_compute_catalog
: debug-x86-64test_idle_checkpoints
: debug-x86-64Flaky tests (2)
Postgres 17
test_read_validation
: release-x86-64Postgres 16
test_sharding_backpressure
: release-x86-64Test coverage report is not available
277c33b at 2024-11-27T11:12:11.403Z :recycle: