@kamalg16584248 The performance degradation in your StreamBatch run after moving Kafka to an MSK (Amazon Managed Streaming for Apache Kafka) cluster in Pega 8.8 is likely due to configuration mismatches or network latency. MSK may have different default settings compared to your previous Kafka setup, such as batch size, fetch size, or replication factors. First, ensure the Kafka consumer and producer configurations in Pega are optimized for MSK (e.g., increase fetch.max.bytes, max.poll.records, or tune linger.ms). Also, check if your MSK cluster is in the same VPC and region as your Pega nodes to avoid network delays. Enable debug logging to identify slow points in the stream run. Finally, evaluate your partition strategy—ensure enough partitions exist to parallelize processing efficiently. A side-by-side comparison of the previous and current Kafka settings can help pinpoint the exact cause of the delay.