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

Tasks/background system #209

Open
lenisko opened this issue Dec 3, 2023 · 0 comments
Open

Tasks/background system #209

lenisko opened this issue Dec 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@lenisko
Copy link
Collaborator

lenisko commented Dec 3, 2023

Every time and CPU consuming operation should be placed on the task queue.

Few things to consider:

  • On addition, unique task-id should be returned and saved to database along with input data and options we have chosen.
  • Configuration option where we pick how many workers we would like to be spawned and process our tasks at once.
  • New UI page with a list of currently queued tasks, passed arguments and maybe a few finished with results? Ability to cancel current job (kill), remove others.
  • Button/API call with ability to skip queue - for example, when we process a small area and need a results asap.

In case of current implementations, it might be required to create two-way communication between Koji and Golbat / Dragonite - so when tasks are sent by Golbat, Koji would call it back with results. Otherwise, additional calls with task-id might be sent in a loop till we get an answer.

@lenisko lenisko added the enhancement New feature or request label Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant