-
Notifications
You must be signed in to change notification settings - Fork 14
Report host stats on TPCH benchmarks #131
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
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
b23c0c7
Add support for in-memory TPCH tests
gabotechs aa7fc0d
Add --threads and --workers options in tpch benchmarks
gabotechs 8a27e9b
Remove useless stuff
gabotechs 6a17cca
Automatically resolve tpch paths
gabotechs dab7670
Draft: spawn workers correctly in different tokio runtimes
gabotechs 33ba32d
Register tables only in one place
gabotechs ded5a8c
Spawn benchmark workers as a separate command
gabotechs 0f83b86
Rollback unnecessary changes in localhost.rs
gabotechs 76120df
Add run script
gabotechs e929279
Report host stats on benchmarks
gabotechs b974e5d
Default partitions to threads
gabotechs ebb570e
Pass through arguments
gabotechs 49febe4
Merge branch 'gabrielmusat/tpch-threads-and-workers' into gabrielmusa…
gabotechs 688c6c8
Merge branch 'main' into gabrielmusat/report-host-stats-on-benchmark
gabotechs b87bb0c
Also log tasks per query
gabotechs 0c321ce
Add comment
gabotechs File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the number of cores per worker or total of cpu cores of all workers?
Is there any constraints between this and number of threads per worker? Should number of threads per worker < CPU cores per worker? Is there any enforcement or unexpected behavior if it is not enforced
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Total CPU cores available in the machine that runs the benchmarks
Only the ones specified by the people running the commands, it's possible to do --threads 1000 in a 2 core CPU machine. It does not make much sense to do that though...
Assuming
get_available_parallelism()returns the number of CPU cores in the machine, I think so yes. As these are just benchmarks meant to be run by us, I think it's fine to not do any enforcement in the code, hopefully people running the benchmarks know what they are doing if the do --threads 1000 in a 2 core CPU machine.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree people who run the benchmark should know what we are doing. Maybe we just help remind them that. How about we add a brief message saying number of threads should be < number of cores and number of partitions should be < number of threads?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a doc comment in the CLI