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

Run OptimizationSolver with controlled core utilization. #163

Open
GaboFGuerra opened this issue Jan 17, 2023 · 1 comment
Open

Run OptimizationSolver with controlled core utilization. #163

GaboFGuerra opened this issue Jan 17, 2023 · 1 comment
Assignees
Labels
1-feature New feature or request 2-important/urgent

Comments

@GaboFGuerra
Copy link
Collaborator

GaboFGuerra commented Jan 17, 2023

User Story

As a user of the OptimizationSolver I want to set the number of neurons per core to control for fluctuations in time per timestep during benchmarking of the solver's time to solution.

Conditions of Satisfaction

  • As a user I can set the number of neurons per core in the SolverConfig
  • The neurons per core in SolverConfig forces the compiler to use it as constraint when computing resources allocation.

Acceptance Tests

  • When the user sets number of neurons in SolverConfig, the capacity constraints of the Compiler get modified accordingly.
  • When running the network, the number of neurons per core does not exceed that set by the user in SolverConfig.
@ashishrao7
Copy link
Collaborator

ashishrao7 commented Jan 17, 2023

I have a feeling that this is not as straightforward as changing one variable in the LOIHI.db file. The configuration limits the number of neurons and number of cx_states per core along with other things. For small problems this might naively work but when we really start pushing the limits this might lead to weird errors.
This might require some kind of small intermediate adapter. This probably belongs to core lava than to lava-opt. There of course needs to be an API change in the lava-opt solver to account for this.

@GaboFGuerra GaboFGuerra removed the 0-needs-review Has to be reviewed. label Jan 24, 2023
@GaboFGuerra GaboFGuerra removed this from the lava-optimization 0.3.0 milestone Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-feature New feature or request 2-important/urgent
Projects
None yet
Development

No branches or pull requests

4 participants