-
Notifications
You must be signed in to change notification settings - Fork 41
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
Reorganize benchmarks/dbscan #1217
Conversation
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 would prefer if we moved the common instantiation things into a library to speed up compilation.
Can you please elaborate? What I'd really like is to be able to specify in CMakeLists.txt which instantiations to do, and not having to edit the source files switch statements. Then, I would just instantiate it for a couple dimensions by default. When needing more, like a paper, I think it would be OK to allow longer compilation times. |
We are compiling the same thing multiple times, one for each exe |
Which thing? |
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.
Minor comments.
Looks good after you fix them.
|
||
add_executable(ArborX_Benchmark_DBSCAN.exe dbscan.cpp) | ||
target_include_directories(ArborX_Benchmark_DBSCAN.exe PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}) | ||
target_link_libraries(ArborX_Benchmark_DBSCAN.exe ArborX::ArborX Boost::program_options cluster_benchmark_helpers) |
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.
target_link_libraries(ArborX_Benchmark_DBSCAN.exe ArborX::ArborX Boost::program_options cluster_benchmark_helpers) | |
target_link_libraries(ArborX_Benchmark_DBSCAN.exe PRIVATE ArborX::ArborX Boost::program_options cluster_benchmark_helpers) |
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.
Doesn't really matter for the executable. We don't do this anywhere else.
Couple builds did not start (HIP, SYCL) but they passed before clang-tidy check, so that's fine. |
The current code mixes different clustering algorithms in a single place. It has many issues:
The main motivation for this cleanup is to prepare for adding a distributed dbscan benchmark.
This PR: