roachtest: limit number of workers for schemachange tests #40924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With
--wait=false
, tpcc defaults to10*W
workers and connections.The opt catalog objects are per-connection, so this ends up using a
lot of memory. The schema change part makes it worse because we keep
multiple versions of the changed tables.
Reduce the number of connections in the tests, at least until we
implement sharing of opt catalog objects between connections.
Fixes #40566.
Release justification: non-production code change.
Release note: None