Chore: Make Resolved Graph GC-able#174
Merged
edwin-grabtaxi merged 1 commit intoApr 6, 2026
Merged
Conversation
edwin-grabtaxi
requested review from
adarsh-grabtaxi,
arnav-grabtaxi,
arunsampathkumar-grabtaxi,
minkuanlim-grabtaxi and
vanminh-grabtaxi
as code owners
arunsampathkumar-grabtaxi
approved these changes
Apr 6, 2026
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
2 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.
Proposed Changes
I observed the behavior of Grazel when running on large project with many variants. During Resolving Dependency phase, the heap is always slowly maxed and GC brings nothing to free the heap. Looking deeper, the whole graph of resolved component are retained because we mark them as
@Input(example). This is beneficial for caching, but it keeps accumulating and block the other dependency resolution tasks, which defeats the benefit of caching altogether.As we know the dependency resolution is written to the disk after the dependency is resolved, then we know actually the resolved graph can be GC-ed. Marking it as
@Internaland remove the@Cacheabletaskwill make it GC-able, as it not held by gradle to be cached later. This way, when GC happen, we can freed more memory and make way for other dependency resolution tasks to run.Also we add logHeap (can be activated by -Dgrazel.logHeap=true) to monitor the heap usage.
Testing
Issues Fixed