Explore the factors affecting end-to-end latency in RisingWave and provide strategies for optimizing performance.
barrier_interval_ms
system parameter.
In contrast, sink outputs are eagerly written to the downstream system without waiting for barriers to commit.
If your application requires latency ≤ 500ms, we recommend using a sink to trigger event-driven business logic downstream, rather than relying on a built-in materialized view with periodic polling. This ensures faster data availability.
stream_hash_agg_max_dirty_groups_heap_size
prioritize low latency, ensuring changes are sent downstream as soon as they arrive. However, the second-order effect is that it can increase the load on downstream operators, potentially slowing them down due to a higher volume of intermediate results.
stream_hash_agg_max_dirty_groups_heap_size
buffer more updates before consolidating them, which reduces redundant computations and minimizes intermediate results—at the cost of slightly increased latency.