search

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.
https://go.risingwave.com/slack
Apache License 2.0
7.09k stars 585 forks source link

Monitor batch query and streaming query I/O metrics separately #8795

Open hzxa21 opened 1 year ago

hzxa21 commented 1 year ago

so that we can better understanding the performance characteristic on storage for batch and streaming query

zwang28 commented 1 year ago

IIUC, after we support dedicated serving cluster(and never serve from streaming cluster), we can achieve this separation by simply tuning grafana a bit?

hzxa21 commented 1 year ago

IIUC, after we support dedicated serving cluster(and never serve from streaming cluster), we can achieve this separation by simply tuning grafana a bit?

True. But I think dedicated serving cluster is optional so it may still be useful to distinguish them.

github-actions[bot] commented 1 year ago

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

fuyufjh commented 1 year ago

Hi, any futher plans?

hzxa21 commented 1 year ago

Hi, any futher plans?

This is low priority since we can use dedicated serving cluster if we found that streaming and batch are interfering with each other. I will remove it from the milestone for now.