We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It doesn't seem to be heap or cpu bottleneck. So what is the actual bottleneck, is it IO cost, due to lookups? If so we need a metric for it.
Or is it skew? because in some scenarios, the workload peaks at 1600%. But we have 32 cores.
Needs further investigation.
The text was updated successfully, but these errors were encountered:
Some workloads to test:
Measurements:
Sorry, something went wrong.
RC optimized group top n. This fixed the issue.
kwannoel
No branches or pull requests
It doesn't seem to be heap or cpu bottleneck. So what is the actual bottleneck, is it IO cost, due to lookups? If so we need a metric for it.
Or is it skew? because in some scenarios, the workload peaks at 1600%. But we have 32 cores.
Needs further investigation.
The text was updated successfully, but these errors were encountered: