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

[FEA] Need capability for defining runtime requirements on MIS, and MIS should be able to serve an algorithm in "always on", "when requested" or "batch modes", as specified by the developer #227

Open
GreySeaWolf opened this issue Dec 11, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@GreySeaWolf
Copy link
Contributor

Is your feature request related to a problem? Please describe.

This is related to managing app running requirements on the MIS

Describe the solution you'd like

Need the capability of running apps on multiple run time scenarios: 1) ALways on, an input may come any time, need to respond fast; 2) Bring it up when requested, and the algorithm will execute and after completing its task it can be taken down until next request, 3) In batch mode, periodically the algorithm can be brought online to work on every task accumulated so far, and after completing its tasks it can be taken down until its next scheduled task.

Describe alternatives you've considered

Additional context

@GreySeaWolf GreySeaWolf added the enhancement New feature or request label Dec 11, 2021
@GreySeaWolf GreySeaWolf changed the title [FEA] Need capacity for defining runtime requirements on MIS, and MIS should be able to serve an algorithm in "always on", "when requested" or "batch modes", as specified by the developer [FEA] Need capability for defining runtime requirements on MIS, and MIS should be able to serve an algorithm in "always on", "when requested" or "batch modes", as specified by the developer Dec 11, 2021
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