-
Notifications
You must be signed in to change notification settings - Fork 1
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
Define measure of persistence #44
Comments
@lifflander @PhilMiller @nlslatt The Coefficient of Variation (CoV) appears to work well for our purpose, when computed over a sliding window. This is the ratio of stdev/mean (assuming mean >0 which shall always be the case for us as no object will have 0-time associated to it). There is more “accumulated variation” as the size of the sliding window increases, which is to be expected, while at the same time the CoV becomes smoother. But in all case they seem to yield comparable results. So we should favor the smaller windows as they are faster to compute. My proposal for a measure of persistence : coefficient of variation (which we can maintain locally on each object at very limited cost, say over a 4-long sliding window), averaged out across all objects each time we want to attempt a LB stage. If it’s greater than 10%, then pass (postpone) the LB. Maybe postpone it by at least the length of the sliding window, to avoid unnecessary global averaging. |
Quite a bit of research was done on this, 5 years ago, but it seems @lifflander that there isn't any longer a need to keep this open. We should probably write a short summary of the what was developed/tested (in case persistence-based LB is needed again) and close this one -- and transpose it into a vt issue. |
This is closed and superseded by vt #2303 |
The main goal of this issue is to determine when it the "persistence" assumption (needed for statistically-based distributed LB) is satisfied so such LB can be efficiently performed
The text was updated successfully, but these errors were encountered: