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

Support checkpointing on IndexSolver #58

Open
Ant1ng2 opened this issue Oct 15, 2020 · 0 comments
Open

Support checkpointing on IndexSolver #58

Ant1ng2 opened this issue Oct 15, 2020 · 0 comments
Assignees
Labels
help wanted Extra attention is needed [Solver] IndexSolver Issues referring to IndexSolver

Comments

@Ant1ng2
Copy link
Contributor

Ant1ng2 commented Oct 15, 2020

The IndexSolver is currently a wrapper around the GeneralSolver. It solves using the GeneralSolver in one go, meaning it solves everything in-memory and then writes everything in a file. Obviously this is not optimal.

Let's start by optimizing the "one go" part. Modify the IndexSolver to support checkpointing. More specifically, we want the IndexSolver to store its state (perhaps through pickling) after fulfilling some criteria (decided by the implementer). What's more, the IndexSolver should be able to recover its state from its last checkpoint and continue solving.

When recovering from the last checkpoint, it's ok to load the entire file into memory. That'll be fixed in a later issue.

@Ant1ng2 Ant1ng2 added help wanted Extra attention is needed [Solver] IndexSolver Issues referring to IndexSolver labels Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed [Solver] IndexSolver Issues referring to IndexSolver
Projects
None yet
Development

No branches or pull requests

2 participants