-
Notifications
You must be signed in to change notification settings - Fork 2
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
What high priority scheduler issues remain to be resolved? #197
Comments
I have the list of open bugs which are -qdel -t doesn't work #167 (workaround however exists) I've suggested a review of fairshare configs as the most "common" item that is referenced. |
Ah, and #186 may be a bug but it may not be. I'm not sure on that one either. |
#147 also lists a number of open issues in addition to these:
|
Yep, I've already got those in the collection with them. |
Fairshare BTW does take group membership into account. So I'd like further explanation or example where it is not as believed to be. |
We can probably also address #102 to optimize scheduling order |
OK, I think @tatarsky has the best handle on the order of priority here at this point. I'll write back to Rob and let him know you have a good idea of what order to tackle these things. Thanks! |
Yes, I wanted to basically comment out "ENABLEHIGHTHROUGHPUT TRUE" on that one and see if it improves or degrades the situation. But I'm trying to only make one mod at a time ;) |
We are reviewing items and may make some one at a time changes at some point. But if we do they will be announced with a Git issue so that any issues with the mod can be tracked. This is unrelated to core dump matter. Which remains under investigation. |
All items in this ticket are duplicated in other Git tickets or resolved. |
We have sometime left with Adaptive Computing to resolve additional issues.
Besides the scheduler segfault issue (#172), what other high priority issues do we have?
The text was updated successfully, but these errors were encountered: