RE: [Eng-Spa] Process or Task Management at the Middleware Layer
You are viewing a single comment's thread:
I apologise for the delay in reading and commenting out your blog. Last week my life was hectic, as I mentioned already in several blogs of others and myself. I hence got some delay with my activities on chain. I am now slowly clearing the stack of posts that I noted as interesting for a read, and here I am!
First, I would like to thank you a lot for this instructive post. Next, I have a small question. I am wondering about the cost in resource to move some running job back to a ready mode, and vice versa. Could this be a problem if we have tons of jobs running? Thanks in advance for your answer.
0
0
0.000
Hi @lemouth. Processes or tasks can be in one state at a time, the detail lies in what happens behind the scenes.
In the architecture of the processor, several modules must work, activate, deactivate, store, etc. Then, the performance and associated cost is increasing, as tasks are running in parallel, which is the norm nowadays.
That is, we have multiprocessing and tasks running simultaneously on different processor cores, which consumes energy, time, and resources. Thank you for establishing this communication.
Mmmmh I see. Thanks for the clarification!
Cheers!