About the UCR document, here are some comments:
- I’m not sure that I understand U1. It says the user doesn’t care how PBS allocates the cores. That seems to translate to “use the default PBS behavior while scheduling my job”, right? If so, then I’d suggest that we just document the default behavior in the design doc and maybe not treat this as a use case.
- In the second half of U3, you might want to either say something generic, like “the user should be able to specify placement strategy for their job on the logical cores”, or list out all the placement strategies that they can specify, ‘pack’ seems to be just one of them as you’ve mentioned ‘scatter’ in one of the examples.
- U5 doesn’t seem like a new use case to me. Isn’t that what PBS does now anyways? Yes, you’ll have to enhance the functionality to deal with logical cores, but as far as the general use case goes, I think it is already a part of PBS. What do you think?
All of these seem like use cases for users who submit jobs, do we need any use cases for the admins? They’ll be the ones configuring the nodes for hyper-threading right?