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

Engines processes should be persisted #40

Closed
franciscoBSalgueiro opened this issue Oct 15, 2023 · 0 comments · Fixed by #41
Closed

Engines processes should be persisted #40

franciscoBSalgueiro opened this issue Oct 15, 2023 · 0 comments · Fixed by #41

Comments

@franciscoBSalgueiro
Copy link
Owner

franciscoBSalgueiro commented Oct 15, 2023 •
edited

Currently, for simplicity, engine processes are restarted on every position or settings change. However, they should be kept alive and the changes to position and settings be done through the uci protocol (#11 (comment))

Problems:

  • Avoiding leaks: processes should be killed when no longer needed (e.g. tab is closed)
  • Engine should be restarted if it quits unexpectedly
  • Should evaluations for previous evaluated positions be cached in some way? Maybe optionally allow to re-run the engine?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Engines processes should be persisted franciscoBSalgueiro/en-croissant
1 participant
@franciscoBSalgueiro