-
Notifications
You must be signed in to change notification settings - Fork 590
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
perf: nexmark q14 #8503
Comments
RW Blackhole:
|
I guess this might be caused by a similar issue to #5130. We need to evaluate a lot of risingwave/src/expr/src/expr/expr_binary_nonnull.rs Lines 359 to 401 in c907a56
|
I am not sure if the behavior here is proper. we have |
According to the grafana dashboard and @fuyufjh, we inspected that the CPU is not fully utilized. Occasionally I encounter segmentation faults or bad performance on Mac only for Nexmark Q14. Considering #6205, I'm extremely suspicious that it's caused by the backtrace capture here: when we try to extract the risingwave/src/expr/src/vector_op/extract.rs Lines 51 to 58 in 8183b41
|
The CPU ultilization looks good after #8538. Let's wait for next performance report. (parallelism = 4) |
Running Q14 right now as the last night's performance test failed |
OK, now it's 893.8K 😆 But as
we still keep this open? |
LGTM. I guess there won't be significant difference (compared to the "backtrace" one 😄), but it's indeed a possible optimization. |
Since #9052 tracks the only left undone issue, we close this issue now. |
Query:
RW:
Flink:
The text was updated successfully, but these errors were encountered: