-
Notifications
You must be signed in to change notification settings - Fork 43
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
Fix #81 Block_Info::read_block_costs(): use more realistic RAM estimate #82
Conversation
Looks good to me! Have you checked that this improves memory distribution for the timing run in some cases? |
I've made several runs (on First case shows better RAM distribution for new costs. Except for the (mysterious) first case, we see that both approaches yield similar RAM variation. Why?
To obtain really different results, one has to consider a problem where, e.g., positive semidefinite blocks contribution P.S. Even we do not observe a major difference here, I think that we should use the new RAM estimate, because (if we got it right) it should work well for a broader range of problems. |
BTW I found a case when RAM distribution per cores remains highly non-uniform even for actual step.
|
#81
This improves block distribution among the cores during timing run only.
We use the same RAM estimate as in #83,
2#(B) + 5#(PSD) + 2#(S) + 2#(Bilinear pairing)