John Spray 41ee75bc71 pageserver: do config writes in a spawn_blocking (#5603) ...

## Problem

We now persist tenant configuration every time we spawn a tenant. The
persist_tenant_config function is doing a series of non-async filesystem
I/O, because `crashsafe::` isn't async yet. This isn't a demonstrated
problem, but is a source of uncertainty when reasoning about what's
happening with our startup times.

## Summary of changes

- Wrap `crashsafe_overwrite` in `spawn_blocking`.
- Although I think this change makes sense, it does not have a
measurable impact on load time when testing with 10k tenants.
- This can be reverted when we have full async I/O

2023-10-23 09:19:01 +01:00

..

benches

walredo: make request_redo() an async fn (#5559)

2023-10-18 11:23:06 +01:00

ctl

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00

fixtures

walredo: simple tests and bench updates (#3045)

2023-01-16 18:24:45 +02:00

src

pageserver: do config writes in a spawn_blocking (#5603)

2023-10-23 09:19:01 +01:00

Cargo.toml

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00