Experiences with ClickHouse hot/cold storage for Plausible CE?

[RazerPie]

Hi,

I'm planning a self-hosted Plausible CE deployment and I'm looking into long-term CLickHouse storage options.

Traffic will be somewhat seasonal, potentially around 10M+ pageviews/moth durin busier periods, while much lower during quieter months. I'd like to keep historical analytics indefinitely, but I don'n necessarily want severl years of rarely accessed data occupying the fast local storage.

I'm considerin setup along these lines:

• Recent data on local NVMe
• Older data moved to slover/cheaper storage
• CLickHouse storage policy with TTL .. TO VOLUME

So conceptually:
Local NVMe - recent data, 0-12 months
↓ TTL MOVE
Slower storage - historical data +12 months

I'm mainly interested in whether anyone is already doing something similar with Plausible CE in production.

A few specific questions:

1. Has anyone configured events_v2 ans sessions_v2 with hot/cold ClickHouse sotrage policies?
2. If so, what storage backed are you using for the cold tier: another local disk, network/block storage, etc?
3. Have you encountered any issues with Plausible upgrades or ClickHouse migrations after adding custom storage policies or TTL rules?
4. Does Plausible expect these tables to use the default storage policy, or is using a custom policy considered reasonably safe?
5. Is CLICKHOUSE_DEFAULT_STORAGE_POLICY intended to support setups like this?
6. Are there any Plausible-specific reasons why moving older parts to slower storage would be a bad idea?
7. For people running larger self-hosted instances, how do you normally manage long-term historical data?

I'm not mainly looking to delete old analytics. The goal is to keep them queryable while allowing older, rarely accessed data to live on cheaper/slower storage.

Any production experiences, configuration approaches, or upgrade-related caveats would be very useful. : )