RisingWave Community - What kind of cluster sizing is necessary to handle aggregation queries over a Kafka topic with historical data?

Recommend trying at least 16 CPU for the compute node, especially during the stage of reading historical data to build the materialized view.
Use as many CPUs as possible to shorten the period before the MV catches up with the latest data.
After the MV catches up with new data, scale in the resources to accommodate the throughput of new data.
Put as much work as possible into the materialized view to simplify queries for tools like Superset.
Going vertical (increasing resources on a single node) is preferred to avoid network overhead, but consider a mix of vertical and horizontal scaling for cost-effectiveness in cloud environments like EC2.