The iFogSimToolkit (with its new release iFogSim2) for Modeling and Simulation of Resource Management Techniques in Internet of Things, Edge and Fog Computing Environments. In the new release Mobili Management, Microservice Management, and Dynamic Clustering mechanisms are added as new features.
While I think, First, it should calculate FinishedSoFar(which has happened based on the previous mipshare of the VM), then update the mipsshare of the VM (to calculate the processing time of the remaining length based on the new mipsshare).
Would you please check this and let me know if we should move line 70 after that?
iFogSim (V1 and V2) is built on top of Cloudsim Engine. The CloudSim Engine is tested and the aforementioned concern does not create any issues.
Hope it helps.
When updating the other VM processing, first, it sets the new mipsshare of the VM In the following line: https://github.com/Cloudslab/iFogSim/blob/fca02da0132d155754373402e72ccaed5aca3d71/src/org/cloudbus/cloudsim/CloudletSchedulerTimeShared.java#L65
Then, it calculates the FinishedSoFar in line 70: https://github.com/Cloudslab/iFogSim/blob/fca02da0132d155754373402e72ccaed5aca3d71/src/org/cloudbus/cloudsim/CloudletSchedulerTimeShared.java#L70
While I think, First, it should calculate FinishedSoFar(which has happened based on the previous mipshare of the VM), then update the mipsshare of the VM (to calculate the processing time of the remaining length based on the new mipsshare).
Would you please check this and let me know if we should move line 70 after that?
Best, Saeedeh