search

risingwavelabs / risingwave

SQL stream processing, analytics, and management. We decouple storage and compute to offer efficient joins, instant failover, dynamic scaling, speedy bootstrapping, and concurrent query serving.
https://www.risingwave.com/slack
Apache License 2.0
6.62k stars 544 forks source link

Per executor metrics for computation and IO #10054

Open kwannoel opened 1 year ago

kwannoel commented 1 year ago

it makes me wonder how we monitor and determine the bottleneck in a streaming job, e.g. which executor i.e. the one that spent largest percentage of the time (include time for both computation and IO)? Is it a good definition Not sure if this is tracked on any panel on Grafana

Posted by @lmatz originally.

Per executor metrics for:

Graph should have executor type labelled too.

Currently our approach to identify bottleneck seems to be using:

  1. flamegraph
  2. guess and check with different queries with and without particular executors.

Which can be made more efficient with the above suggestion.

github-actions[bot] commented 2 weeks ago

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄