Finding Core Number On Queue and LSF

  • Thread starter Thread starter Soaring Crane
  • Start date Start date
  • Tags Tags
    Core Queue
AI Thread Summary
The discussion centers on using the bqueues command in LSF to determine the maximum number of cores available for a specific queue. It highlights that LSF operates on broader concepts than just core counts, focusing instead on "processors" and "processor slots." Each job can run across multiple computers with varying hardware configurations, making it essential to understand that the number of processors does not directly correlate to physical cores. LSF does not manage how jobs utilize multiprocessing or multithreading once they are running, leaving it to users or administrators to control resource allocation through scripts or environment variables. This reliance on user compliance raises concerns about potential misuse of system resources.
Soaring Crane
Messages
461
Reaction score
0
I’m trying to find out the largest number of cores that can be used on a specific queue in LSF with the bqueues command. I’ve used the option –l after reading the manual, but I don’t see any information about cores listed. Any suggestions?

Thanks.
 
Technology news on Phys.org
It's a while since I used LSF, but IIRC, LSF works with more general concepts than "number of cores". Remember one LSF job queue might be starting jobs on several different computers with different hardware specifications, and also one LSF job might be running in parallel on several computers (not just several cores of one computer).

LSF has the concept of the number of "processors" that a each computer has, and the number of "processor slots" that each job requests. It's up to the humans who configure LSF how to map those onto the actual hardware available. For example the number of "processors" might be used as measure of different CPU speeds on different single-processor computers, not necessarily the number of physical cores.

IIRC LSF doesn't know anything about how a job uses multiprocessinig or multi-threading once it is running. If you want to control that (e.g. run four job streams with 4, 2, 1, 1 cores available on a single 8-core machine) either you have to trust your users not to abuse the system, or you write shell scripts to set the approporiate environment variables or whatever, to tell and/or enforce what resources a program can use when it runs. That still means trusting the software developers to do it right - and of course the users and developers may be the same people, in sone situations.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
I tried a web search "the loss of programming ", and found an article saying that all aspects of writing, developing, and testing software programs will one day all be handled through artificial intelligence. One must wonder then, who is responsible. WHO is responsible for any problems, bugs, deficiencies, or whatever malfunctions which the programs make their users endure? Things may work wrong however the "wrong" happens. AI needs to fix the problems for the users. Any way to...
Back
Top