Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Investigate robustness of determine_queue.cwl #16

Open
thomasyu888 opened this issue Aug 29, 2021 · 1 comment
Open

Investigate robustness of determine_queue.cwl #16

thomasyu888 opened this issue Aug 29, 2021 · 1 comment
Assignees

Comments

@thomasyu888
Copy link
Contributor

thomasyu888 commented Aug 29, 2021

If there are concurrent submissions running on the main queue, the determine queue doesn't seem to do a good job of fanning out submissions.

It doesn't seem to be an issue if you just run one submission at a time on the main queue, but theres a minute overhead per submission...

@vpchung
Copy link
Member

vpchung commented Sep 3, 2021

I've tested with multiple concurrent submissions throughout the day and it seems to be working fine, though I do notice a bias for Internal Queues 1 and 2.

Will continue testing to know for sure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants