Removing julia versions and updating scripts to checkout from mmtk/julia instead
#1
Conversation
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
added 12 commits
May 19, 2025 05:49
…ddress-based hashing for now)
|
Cool, thanks. Could you share what output you get after running these scripts? I'm also curious about what the fragmentation numbers look like for these GCs. |
|
The problem is that @qinsoon recently changed the mmtk-julia repo to add address-based hashing, but there's a bug somewhere we're trying to figure out. I've got some plots with a fixed heap size, but I'm not sure how reliable they are, and if they're even comparable to the stock GC without a fixed heap. Note that the changes above are not setting a fixed heap for the stock GC. With max copying: With non-moving: |
|
What benchmark is this for? |
|
I have also collected some data about the block histogram: Block Histogram (Pinned objects per block)
Object Type Pinning Stats
Nonmoving Object Type Reachability Stats
Pinned Object Types in Single-Pinned Blocks
|
The Inference benchmarks. |
|
This branch builds Julia with using a copy of mmtk-julia in this repo, which does not have the recent changes in EDIT: I am not sure if there are other differences between the copy of mmtk-julia and our developing branch. One difference that I noticed is that |
|
Agree with @qinsoon: given that we're now fetching the Julia repos, it would make sense to also fetch the Also, IIUC, these scripts will run the benchmarks with the HEAD of each branch. This is fine for now, but it would be nice to have a way of specifying a commit in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR removes all the old copies of julia and mmtk-julia, leaving only the latest
mmtk-julia(with a change that prints out the utilization after each GC, necessary for the logs.Instead of having the fixed versions, it should download the latest version of
mmtk/juliausing themmtk-support-moving-upstreambranch as default. It should clone different versions of julia:julia-immix-max-moving(which copies every object that can be copied at every GC)julia-immix-always-moving(which makes every GC a defrag GC)It should then run the benchmarks as usual considering all these variants.