Split test/device/random.jl into multiple files#233
Closed
AntonOresten wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
The failing test is unrelated, but confusing... EDIT: perhaps related to https://developer.nvidia.com/blog/nvidia-cuda-13-3-enhances-gpu-development-with-tile-programming-in-c-compiler-autotuning-and-python-updates ? Did something get bumped? Resolved in #234 |
9dc66ea to
3823563
Compare
Collaborator
Author
|
|
Member
|
Maybe use subdirs? |
Member
|
Actually, I'll try optimizing the compiler first. Maybe this isn't necessary. |
maleadt
added a commit
that referenced
this pull request
May 28, 2026
As observed in #233, compilation of large kernels is slow. The culprit turned out to be the user/use lookup, which walks the entire IR every time since our IR doesn't encode use-def chains (as opposed to LLVM or MLIR). To avoid this cost, introduce a Rewriter abstraction that caches these lookups while invalidating them upon insertion, mutation, etc. Once again modeled after MLIR.
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
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.
Most files in the test suite are on the high end 30-60 seconds, but I've noticed the random number generation tests take a disproportionate amount of time, at around 2-5 minutes, and allocating a total of 78 GB on the CPU:
See latest buildkite run (v1.12)
Link: https://buildkite.com/julialang/cutile-dot-jl/builds/400/canvas?jid=019e6496-64bc-4264-8c4f-a61c88f04090&tab=output
This PR splits them up into multiple files so it can leverage ParallelTestRunner.
I also looked into reusing the broadcasted
PHILOX_M/PHILOX_Wconstant tiles across rounds, which made things 5-10% faster:Click to expand
So it seems it's dominated by codegen, but I don't plan on tackling that here.