perf: materilaize can handle conflict for multiple chunks

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

6.79k stars 562 forks source link

perf: materilaize can handle conflict for multiple chunks #13350

Open st1page opened 10 months ago

st1page commented 10 months ago

when handling conflict, materialize executor uses some temporal hashMap structures. It could be more efficient when batching more data

github-actions[bot] commented 1 month 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. 😄