-
Notifications
You must be signed in to change notification settings - Fork 70
[feat] planner: pick dynamicemb HYBRID vs CACHING from topology budgets #508
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
Open
tiankongdeguiji
wants to merge
15
commits into
alibaba:master
Choose a base branch
from
tiankongdeguiji:dynamicemb-hybrid-caching-planner
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,142
−162
Open
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
ffc0325
[feat] dynamicemb planner: mode-aware storage formula (HYBRID vs CACH…
tiankongdeguiji ead7df2
[feat] dynamicemb planner: mode-aware perf model (CACHING bw >= HYBRID)
tiankongdeguiji c88c4f4
[feat] dynamicemb planner: enumerate { HYBRID, CACHING } × factors
tiankongdeguiji 6ce464b
[feat] dynamicemb planner: 2D DP over HBM × DDR
tiankongdeguiji 7187c2a
[test] dynamicemb planner: end-to-end enumerate + DP integration test
tiankongdeguiji c3bff19
[fix] dynamicemb planner: refine storage docstring + simplify perf wr…
tiankongdeguiji 38bd7ad
[fix] dynamicemb planner: per-option DDR prune against per-machine cap
tiankongdeguiji 70b0fcb
[refactor] fold dynamicemb e2e tests + rename DP proposer test + bump…
tiankongdeguiji c28e2b2
[fix] dynamicemb planner: empirically fitted CACHING vs HYBRID perf c…
tiankongdeguiji 5280156
[fix] drop duplicate empirical-fit comment above the constants
tiankongdeguiji 625e1b7
[fix] dynamicemb planner: drop redundant deepcopy in variant emission
tiankongdeguiji 3ff8be6
[fix] dynamicemb planner: cap 2D DP per-axis bins to avoid multi-host…
tiankongdeguiji 984d0df
[doc] dynamicemb planner: tighten three docstrings to match implement…
tiankongdeguiji 08563bb
[test] dynamicemb planner: multi-table DP + legacy alias + empty sear…
tiankongdeguiji 0c0d3d7
[fix] dynamicemb planner: restore cache_params in finally + direct wr…
tiankongdeguiji File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sharp discontinuity at
x=1.0. HYBRID@x=0.99 →0.1199; HYBRID@x=1.00 →1.0— an ~8× jump for a 1% ratio change. The DP will reliably prefer x=1.0 over x=0.99 by a huge perf margin, then prefer CACHING@x=0.5 (0.285) over HYBRID@x=0.9 (0.119) even on workloads where HYBRID@0.9 is plainly faster in reality. If the empirical sweep really shows a step at x=1.0 because the runtime drops the host tier, please call that out as "x=1.0 = HBM-only kernel, not the same algorithm as x=0.99" — and consider whether the enumerator should emit a discretemode={HBM_ONLY, HYBRID, CACHING}axis rather than packing the discontinuity into the samexknob.