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

Incomprehensible benmark results from two dfbenchs built in different dirs #11807

Open
Rachelint opened this issue Aug 4, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@Rachelint
Copy link
Contributor

Rachelint commented Aug 4, 2024

Is your feature request related to a problem or challenge?

I found a extremely strange different results from two dfbench binaries...

  • The first one is built by running cargo build --release --bin dfbench in datafusion dir.
  • The second is built by running cargo build --release --bin dfbench in datafusion/benchmarks dir.

And in my local, I found in main branch:

  • The first one cost 9200+ms when running q22 in clickbench.
  • The second one cost 8800+ms when running q22 in clickbench.

In my branch in #11802

  • The first one cost 8800+ms when running q22 in clickbench.
  • The second one cost 9200+ms when running q22 in clickbench.

Describe the solution you'd like

I want to know why... It confused me much...

Describe alternatives you've considered

No response

Additional context

No response

@Rachelint Rachelint added the enhancement New feature or request label Aug 4, 2024
@Rachelint Rachelint changed the title Incomprehensible benmark results from two dfbenchs built in different dir Incomprehensible benmark results from two dfbenchs built in different dirs Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant