-
Notifications
You must be signed in to change notification settings - Fork 102
question #19
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
Comments
The resource can be released. You can see it in line 332, env.py. |
@HuongDM1896 Sorry, I was wondering if the resource is released every step in an episode, as written in the first five lines in the ddpg_step_forward() function in env.py? |
@Reeseee i think, in every step the resource is released as shown in ddpg_step_forward(). But, u can see, they didn't release total resource, only release the resources of completed tasks. Then they also updated the resources as shown in the next lines of this function. I just only find one time when they release the all resource to full capacity in def release(self). |
@HuongDM1896 :)Thanks,I got it .It seems like it maintain the edge servers' user group across the step, and if the offloading target of the user' request unchanged then it continue using the resource otherwise tries to migrate the request.So when a user's task is completed, it will just simply be removed from the user group of a specific server and won't allocated resource to it next step, is this right? |
Hello davidtw0320! I would like to ask, when you allocate resources, will the total resources in an episode always decrease or will there be a process of resource release?
The text was updated successfully, but these errors were encountered: