Skip to content
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

Multimember execution is resource expensive #58

Open
scarlehoff opened this issue Oct 13, 2021 · 0 comments
Open

Multimember execution is resource expensive #58

scarlehoff opened this issue Oct 13, 2021 · 0 comments
Labels

Comments

@scarlehoff
Copy link
Member

I'm not sure how to go around this because multi-member means, by nature, many grids have to be loaded in memory at once (if we want to run the interpolation of all of them) as a result the graph is humongous.

Maybe it actually makes sense to fallback to eager mode in this case. Or to tell the user that's an option.
Admittedly the usual scenario for a MC where vectorization is important is to ask for many values of x (and maybe q) at once, asking for many members (order 100) for a few members of x and q is quick even sequentially so run_eager in this case seems a reasonable option.

@scarlehoff scarlehoff added the 1.3 label Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant