You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a finished VM is re-submitted to start executing again, its arrival time is updated by the broker to the current simulation time, but the creation time is not. It remains the value from the previous submission.
This way, the creation time is smaller than the arrived time for VM resubmissions, causing a negative wait time.
If we just reset creation time to -1, we lose the information about the previous creation time.
The wait time should represent the total time the VM has waited during all the times it was re-submitted to the broker.
Before resetting the creation time, we have to add up the previous wait time to a new totalWaitTime attribute, then reset the creation time. The creationTime and previous waitTime attributes will represent the last time VM was created and last wait time, respectively.
When a finished VM is re-submitted to start executing again, its arrival time is updated by the broker to the current simulation time, but the creation time is not. It remains the value from the previous submission.
This way, the creation time is smaller than the arrived time for VM resubmissions, causing a negative wait time.
If we just reset creation time to -1, we lose the information about the previous creation time.
The wait time should represent the total time the VM has waited during all the times it was re-submitted to the broker.
Before resetting the creation time, we have to add up the previous wait time to a new totalWaitTime attribute, then reset the creation time. The creationTime and previous waitTime attributes will represent the last time VM was created and last wait time, respectively.
Related Issues
The text was updated successfully, but these errors were encountered: