GreptimeTeam/greptimedb

Slow `DROP DATABASE` with large number of metric tables

Opened this issue · 0 comments

What type of enhancement is this?

User experience

What does the enhancement do?

When a database contains a large number of metric tables (thousands), the DROP DATABASE operation becomes excessively slow, taking several minutes to complete. This performance issue is due to the metric engine’s behavior of scanning the metadata region each time a table is dropped. The p50 latency for this metadata lookup is around 300ms, leading to significant delays when dropping numerous tables.

Implementation challenges

No response