Increase cache size #2264
Draft
Increase cache size #2264
+4
−4
Conversation
This file contains 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
Signed-off-by: Anatoly Myachev <[email protected]>
anmyachev
commented
Sep 17, 2024
| # before each kernel call to make sure that the L2 cache | ||
| # doesn't contain any input data before the run | ||
| cache_size = 256 * 1024 * 1024 | ||
| cache_size = 512 * 1024 * 1024 |
There was a problem hiding this comment.
This increases the difference from the upstream, so it will be necessary to come up with a mechanism in Triton itself to parameterize this value.
Note: we can't make this change only in benchmark_testing.py because testing.py file is used for benchmarking upstream PyTorch.
There was a problem hiding this comment.
PyTorch passes device properties. Wondering if we can use info::device::global_mem_cache_size to determine the size of the cache here somehow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checking the impact
CI: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/10890455942
CI: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/10891992012 (without IPEX)
AFAIK clearing 256MB L2 cache isn't enough for our main benchmarking system. The performance numbers get a little worse when increasing this way, however it seems we should do it (not necessary, since we only use one tile).