Re: [Opaltoolkit-users] Specifying the number of processors for a parallel job

[Luca C. <lcl...@uc...>]

Jennewein, Douglas M wrote:
> Hi, Luca:
> 
> I am using the Opal 1.9.3 Rocks roll, and a patch would be great.
> Thanks!
> 
> -Doug
> 

Hi Doug,
we have released Opal 1.9.5 with the cpu input feature.

Attached there is the patch to from 1.9.3 to 1.9.5, although I think 
that this can create some problem. In fact if you have done any 
modification to the opal source code it will fail.

Somewhere next week we will make a new opal roll with this version (I 
would wait for that).
What version of Rocks do you have (32 or 64 bits)?


Luca


> -----Original Message-----
> From: Luca Clementi [mailto:lcl...@uc...] 
> Sent: Wednesday, September 10, 2008 1:52 PM
> To: Jennewein, Douglas M
> Cc: opa...@li...
> Subject: Re: [Opaltoolkit-users] Specifying the number of processors
> foraparallel job
> 
> Jennewein, Douglas M wrote:
>> Hi, Jane:
>>
>>  
>>
>> I looked at the num.procs entry in opal.properties, and determined
> that 
>> if I set num.procs but do not pass the "n" parameter to the generic 
>> service client I get an error saying that I have not specified the 
>> number of processors for a parallel job.  Also, if I set num.procs to
> 4 
>> and then launch an opal job with the generic service client passing it
> 
>> "n 7" to run on 7 processors I get an error saying there are not
> enough 
>> available processors.  But if I specify 4 or fewer processors the job 
>> runs.  This lead me to believe that num.procs is used to specify the 
>> total processors available for opal jobs.  Is that correct? 
>>
>>  
>>
>> -Doug
>>
> 
> Dear Doug,
> you are right.
> 
> num.proc is used to specify the maximum number of proc you want to 
> expose with opal, then you have to specify the number of processors you 
> actually wanna use when you launch a job.
> 
> So for the command line client it is already supported, but not for the 
> web interface.
> 
> What version are you using? I can patch Opal web interface to support 
> that feature and make a new release 1.9.5 in a short time frame (less 
> than a week). This was on my TODO list for a long time.
> 
> Sincerely,
> Luca
>