APS or IRUN multithread = multicore?

Hyperthreading is a capability of Intel processors, and it is enabled/disabled as a BIOS setting usually. So it's a machine setup thing.

If you've allocated a certain number of cores when you submitted the job with LSF, you can use +mt=lsf - and then it will inherit the number of threads from the LSF settings.

There's no need to allocate more threads for HDL aspects - it's only the analog solver that is multi-threaded (that includes any analog parts of HDLs too).

Regards,

Andrew.

Hi Andew, 

Thanks for this, it helped to an extent. I put "lsf" in the multi-threading value in the "Hign Performance GUI", then it took the +mt=lsf automatically.

I wonder, if this can be done in reverse way. When I define multi-treading value, the LSF number should be automatically updated.

The either way I can put is, when I define my mt value in the GUI, the LSF processor should be automatically decided based on the mt value.

Do we have such feature ?

Thanks,

Amar

Hi Andew, 

Thanks for this, it helped to an extent. I put "lsf" in the multi-threading value in the "Hign Performance GUI", then it took the +mt=lsf automatically.

I wonder, if this can be done in reverse way. When I define multi-treading value, the LSF number should be automatically updated.

The either way I can put is, when I define my mt value in the GUI, the LSF processor should be automatically decided based on the mt value.

Do we have such feature ?

Thanks,

Amar

Hi Amar,

This would be putting the cart before the horse. If you've already submitted the job using LSF, then LSF has submitted the job on a machine with sufficient resources to fulfil the resource requirement you asked for. Imagine that you asked for 4 CPUs when submitting the job, and ended up on a machine with 4 CPUs (or maybe 8 CPUs but the other 4 are being extensively used by another job). Now spectre says "hey, LSF, I need 12 CPUs". What's LSF going to do? Plug in some extra CPUs on the machine?

Some queueing systems do have the ability to move a running job to another host (LSF has bswitch to do something like this, but I'm not entirely sure it's about updating the resource requirements), but I recall when looking into this in the past that it needs the application to be able to readdress its memory by being aware of this - which strikes me as being rather difficult and very specific to the queuing system used. So this is not supported (assuming it's even possible - I've not spent enough time investigating it).

So in general, changing the resource requirements after the job has started makes no sense.

Andrew.