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.

Sign up for GitHub

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

Jump to bottom

Consider caching the constraint functions between calls to BudgetOptimizer.set_constraints #1399

Open
ricardoV94 opened this issue Jan 18, 2025 · 0 comments
Open

Consider caching the constraint functions between calls to BudgetOptimizer.set_constraints #1399

ricardoV94 opened this issue Jan 18, 2025 · 0 comments
Labels
MMM optimizer

Comments

@ricardoV94
Copy link
Contributor

ricardoV94 commented Jan 18, 2025 •
edited
Loading

For an iterative workflow we allow changing the constraints used by calling set_constraints, in #1358.

However this will recompile all the constraints (and grad) functions. Would probably be nice to cache them somehow so that if it's the same constraint (based on key?), maybe the id of the constraint function? we don't recompile.

Just keep in mind that caching is the source of all bugs.

CC @cetagostini
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
MMM optimizer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ricardoV94