John Spray 5e3c234edc storcon: do more concurrent optimisations (#10929) ...

## Problem

Now that we rely on the optimisation logic to handle fixing things up
after some tenants are in the wrong AZ (e.g. after node failure), it's
no longer appropriate to treat optimisations as an ultra-low-priority
task. We used to reflect that low priority with a very low limit on
concurrent execution, such that we would only migrate 2 things every 20
seconds.

## Summary of changes

- Increase MAX_OPTIMIZATIONS_EXEC_PER_PASS from 2 to 16
- Increase MAX_OPTIMIZATIONS_PLAN_PER_PASS from 8 to 64.

Since we recently gave user-initiated actions their own semaphore, this
should not risk starving out API requests.

2025-02-21 14:58:49 +00:00

..

client

storcon: don't assume host:port format in storcon client (#10347)

2025-01-10 18:35:16 +00:00

migrations

storcon: use https for pageservers (#10759)

2025-02-20 17:16:04 +00:00

src

storcon: do more concurrent optimisations (#10929)

2025-02-21 14:58:49 +00:00

Cargo.toml

storcon: use jemalloc (#10892)

2025-02-19 14:20:51 +00:00