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

Increase the runner.poll.interval default value #4149

Closed
sphuber opened this issue Jun 4, 2020 · 0 comments · Fixed by #4150
Closed

Increase the runner.poll.interval default value #4149

sphuber opened this issue Jun 4, 2020 · 0 comments · Fixed by #4150
Assignees
Labels
priority/important topic/engine type/performance Issue related to how quickly AiiDA works
Milestone

Comments

@sphuber
Copy link
Contributor

sphuber commented Jun 4, 2020

The current default of 1 can easily lead to unnecessary load on the processor and the PostgreSQL database as the runners will be querying the database for process state every second for each process. This polling mechanism is merely a backup for continuing a process that was waiting on a subprocess in the case it missed the broadcast of the child being done.

@sphuber sphuber added priority/important topic/engine type/performance Issue related to how quickly AiiDA works labels Jun 4, 2020
@sphuber sphuber added this to the v1.2.2 milestone Jun 4, 2020
@sphuber sphuber self-assigned this Jun 4, 2020
@sphuber sphuber changed the title Reduce the runner.poll.interval default value Increase the runner.poll.interval default value Jun 4, 2020
@sphuber sphuber modified the milestones: v1.2.2, v1.3.0 Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important topic/engine type/performance Issue related to how quickly AiiDA works
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant