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

Allow more runs to be queued on cloudsim (limit running not queuing) #652

Open
zwn opened this issue Oct 7, 2020 · 3 comments
Open

Allow more runs to be queued on cloudsim (limit running not queuing) #652

zwn opened this issue Oct 7, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@zwn
Copy link

zwn commented Oct 7, 2020

Currently we can only submit as many simulation as is the limit per team on running simulations. It would be advantageous being able to queue up more simulations to be executed in sequence. So we are proposing to change implementation of the per team limit from limiting submissions to limiting the parallel runs only.

Even better would be to limit the number of AWS machines allocated per team instead.

#644 (comment)

@AravindaDP
Copy link

I would disagree with this proposal and believe current approach is more fair. (Given that I believe simulations are queued in a global queue)

If allowing unlimited queuing is desired, the implementation should be such that each team should have own queue and simulation runner should pick a pending simulation from each team in a round robbin fashion.

@zwn
Copy link
Author

zwn commented Oct 19, 2020

@AravindaDP I believe you might have misunderstood the nature of the proposal. I am not proposing a way for a team to gain advantage in access to the shared cloudsim. I am saying that babysitting the runs is not an effective use of our time.

That said, I was working with the assumption that there are enough AWS resources that each team can have 3 simulations running at any time (which seemed to be the case). If this assumption is correct, than the queuing mechanism does not matter wrt fairness.

@AravindaDP
Copy link

@zwn Apologies I think I misinterpreted your proposal.

It seems both of us are actually referring to same end result with different ways of implementing.

@nkoenig nkoenig added enhancement New feature or request and removed proposal labels Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants