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

Bring ltimes benchmark up to date #1738

Merged
merged 13 commits into from
Oct 11, 2024
Merged

Bring ltimes benchmark up to date #1738

merged 13 commits into from
Oct 11, 2024

Conversation

artv3
Copy link
Member

@artv3 artv3 commented Sep 19, 2024

Summary

This PR bring the ltimes kernel up to date. It is currently a WIP.

@@ -29,7 +29,7 @@ namespace expt
{


template<typename IDX, typename TENSOR_TYPE, camp::idx_t DIM, IDX INDEX_VALUE, strip_index_type_t<IDX> LENGTH_VALUE>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Support for strongly typed indices with TensorIndex was missing, and that is fixed here. We don't have this in our CI testing, so I'll create an issue to add tests for that.

@artv3 artv3 marked this pull request as ready for review October 1, 2024 16:47
@@ -73,6 +73,7 @@ cmake \
-DENABLE_HIP=ON \
-DENABLE_OPENMP=ON \
-DENABLE_CUDA=OFF \
-DENABLE_BENCHMARKS=ON \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make this sort of thing an argument you can pass to the script like we do for compiler version, compute architecture, etc?

shift 3
BENCHMARKS=Off
BUILD_SUFFIX=lc_blueos-nvcc${COMP_NVCC_VER}-${COMP_ARCH}-gcc${COMP_GCC_VER}
fi
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rhornung67 and others, what do we think of doing it this way? If we turn on benchmarks we append a note on the folder name?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine, but I don't think it's necessary. We only have a few benchmark problems, so building them is not a big deal. We could just enable benchmarks in all our scripts and folks can turn them off easily enough if they want. We ill enable them in a subset of CI builds.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That works for me, just to double check. Turn them on for all scripts, and have the command option to turn them off? I'll also leave out the appending note on the folder name. Does that work for all?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think a command line option is needed. We have to edit the build script files to enable/disable features, back-ends, etc. Having a special command line arg for this one case seems confusing and less convenient for me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I can revert and just turn them on across the board. Is this right?

@artv3
Copy link
Member Author

artv3 commented Oct 9, 2024

I think this is good to go now.

@rchen20
Copy link
Member

rchen20 commented Oct 9, 2024

@artv3 Did we want to turn on building ltimes in benchmark/CMakeLists.txt?

@artv3 artv3 enabled auto-merge October 10, 2024 00:31
@artv3 artv3 merged commit a7aa1b4 into develop Oct 11, 2024
26 checks passed
@rhornung67
Copy link
Member

@artv3 if you don't need/want the branch from this PR, please delete. Thank you.

@artv3 artv3 deleted the artv3/ltimes-benchmark branch October 12, 2024 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants