AS per my understanding the main cause is RocksDB's cold cache for index/filter blocks after restore, leading to high latency for initial lookups by the main stream threads. Even if data is in the block cache, the metadata must be loaded from disk. To avoid this, enable index/filter block pinning in the cache, and consider a manual full scan of the GlobalKTable by the main threads before they start processing messages to fully warm the store.