Christian Schwarz 1c88824ed0 initial logical size calculation: add a bunch of metrics (#5995) ...

These will help us answer questions such as:
- when & at what do calculations get started after PS restart?
- how often is the api to get current incrementally-computed logical
  size called, and does it return Exact vs Approximate?

I'd also be interested in a histogram of how much wall clock
time size calculations take, but, I don't know good bucket sizes,
and, logging it would introduce yet another per-timeline log
message during startup; don't think that's worth it just yet.

Context

- https://neondb.slack.com/archives/C033RQ5SPDH/p1701197668789769
- https://github.com/neondatabase/neon/issues/5962
- https://github.com/neondatabase/neon/issues/5963
- https://github.com/neondatabase/neon/pull/5955
- https://github.com/neondatabase/cloud/issues/7408

2023-12-01 12:52:59 +01:00

..

benches

pageserver: refactor TenantId to TenantShardId in Tenant & Timeline (#5957)

2023-11-29 14:52:35 +00:00

ctl

pagectl: add subcommand to rewrite layer file summary (#5933)

2023-11-30 11:34:30 +00:00

src

initial logical size calculation: add a bunch of metrics (#5995)

2023-12-01 12:52:59 +01:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

refactor: use serde for TenantConf deserialization Fixes: #5300 (#5310)

2023-11-30 12:47:13 +02:00