Query performance inconsistent between first and subsequent runs

First query execution takes significantly longer than subsequent executions (7s vs 4s, or 10s vs 4s with more nodes), indicating caching effects or metadata listing overhead on initial run.

Investigate scheduled time and physical input read time metrics to identify whether the difference is due to metadata caching, data caching, or plan caching. Review partition listing performance and file metadata operations in S3.