Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize case of high join amplification #16679

Open
4 tasks
kwannoel opened this issue May 10, 2024 · 0 comments
Open
4 tasks

Optimize case of high join amplification #16679

kwannoel opened this issue May 10, 2024 · 0 comments

Comments

@kwannoel
Copy link
Contributor

In streaming workload, high join amplification can lead to barrier latency spike.

So far our approaches to mitigate these have been more indirect, e.g. decoupling sink, adaptive rate limit. It can isolate the slowness to the specific stream job.

I think we should also explore optimizing join itself.

  • Come up with a high cardinality join scenario, with few columns.
  • Come up with a high cardinality join scenario, with many columns.
  • Observe the flamegraph to see where it can be optimized further.
  • Investigate other systems to see what optimizations can be made in similar situations, e.g. cross join.
@github-actions github-actions bot added this to the release-1.10 milestone May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant