-
Notifications
You must be signed in to change notification settings - Fork 9
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
1265 lb data replay without collection #1720
Conversation
855587d
to
a765426
Compare
Codecov Report
@@ Coverage Diff @@
## develop #1720 +/- ##
===========================================
- Coverage 85.48% 83.98% -1.50%
===========================================
Files 722 776 +54
Lines 25907 27297 +1390
===========================================
+ Hits 22146 22925 +779
- Misses 3761 4372 +611
|
@ppebay I would love to run one of your (load-only) toy problems through this if you can get it into exactly the right json format. Until some changes are made to the json reader, the data effectively needs to be dumped by vt itself (so that the special bits of the object IDs are consistent with vt's usage). |
af9ad32
to
794299d
Compare
auto json = r.readFile(); | ||
auto sd = std::make_shared<LBDataHolder>(*json); | ||
|
||
for (auto &phase_data : sd->node_data_) { |
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.
A minor improvement would be to conditionalize these loops on if (theConfig()->vt_debug_replay) {
This PR allows replaying LB data (workloads) read from json files. It does not correctly handle communications and thus will not work with comm-aware load models or load balancers. To handle communications correctly, a vt refactor where communications are treated analogously to load data by the
ProposedReassignment
load model and theLBManager
would likely be the best approach.Closes #1265