> >> What is the most reliable way to track core-hours, such that occupying 100 >> cores for a day costs 100 times as much as occupying just 1 core for a day? > > Occupying or using?
At the (very) fine grain (as in a context-switching time slice), these two concepts are the same thing because a core can only run one process at a time. But presumably that argument only applies to CPU (or UTIME or STIME) and not to WALLCLOCK time. Even at the coarse grain, we have not seen SGE allocate more jobs to a node than there are cores on that node. Is this where SGE's notion of "slots" comes in? Is a "slot" the same as a core? At the moment, the cluster is swamped with jobs that have brought the load on each node to the point that SGE considers all the queue instances to be in an "alarm" state. Any further jobs are held in the "waiting" state (qw), and qlogin attempts are simply rejected. So certainly in a case like this, I would say that our resources are occupied. ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. ================================= _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
