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

Implement Ceiling of RAM/CPU of BPMNs, per worker #62

Open
galenatjpl opened this issue Oct 5, 2021 · 0 comments
Open

Implement Ceiling of RAM/CPU of BPMNs, per worker #62

galenatjpl opened this issue Oct 5, 2021 · 0 comments

Comments

@galenatjpl
Copy link
Contributor

galenatjpl commented Oct 5, 2021

Ceiling of "weight" (CPU/RAM) of processes on a worker.
BPMNs would be given a "weight" ahead of time, by a human. This could be determined by experimentation and testing of a workflow (means instead of maxes might want to be used here, but up to the human). If a weight is not available (not assigned), then a BPMN would just automatically be assigned a default weight. It would be just metadata about the BPMN. So somebody might say "edrgen.bpmn takes about 0.5 GB RAM, and uses about 30% CPU". So maybe there are two weights :
1). CPU worst case estimate,
2). memory worst case estimate.

And maybe you just can't exceed the machine's capacity by both of those measures.
The worker node would have to define a

  • maxCpu
  • maxMem.

When implementing this, one must be cognizant of the possibility that certain BPMNs may be starved out.

CURRENT PROJECT WORKAROUND: spend more money, and beef up worker instance classes, so that the worker can handle load.

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

No branches or pull requests

1 participant