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

stop/resume jobs #15

Open
c-cube opened this issue Nov 6, 2019 · 1 comment
Open

stop/resume jobs #15

c-cube opened this issue Nov 6, 2019 · 1 comment

Comments

@c-cube
Copy link
Member

c-cube commented Nov 6, 2019

  • when starting a job, put its full serialized description into a dotfile, and append each individual result as we go (use cbor+decoders?)
  • command to list interrupted jobs
  • command to resume an interrupted job (subtracting already done individual tasks)

edit: in xdg rundir, save a description of the job (a flat json file) and append results as we go. remove file when we're done.
resume looks for such files and picks up where ti stopped.

@c-cube
Copy link
Member Author

c-cube commented Dec 5, 2019

after #23 :

  • create a database as soon as we start the bench
  • use a table for "tasks", use it as a queue for workers (with transactional get-and-remove? see what redis does). Tasks include:
  • if we kill the benchmark system, it just resumes from the list of tasks that resumes

In a way all the state is in the sqlite db from the start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant