You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find some trivial (and obviously irrelevant) changes to UTF8 validation code may cause big variances to benchmark result.
UTF8 validation functions are inlined and called directly in benchmark. The compiler may try to optimize them together with the benchmark loop.
Un-inline the benchmark-ed functions makes the result predictable and explainable.
I find some trivial (and obviously irrelevant) changes to UTF8 validation code may cause big variances to benchmark result.
UTF8 validation functions are inlined and called directly in benchmark. The compiler may try to optimize them together with the benchmark loop.
Un-inline the benchmark-ed functions makes the result predictable and explainable.
Reporter: Yibo Cai / @cyb70289
Assignee: Yibo Cai / @cyb70289
PRs and other links:
Note: This issue was originally created as ARROW-14269. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: