[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [condor-users] multiple cpu's
Seems likely to be true, while it is strange.
Condor thinks that first CPU is claimed, while the second is used by the
owner, right? I don't think it is related to your fork, since startd
daemon, which monitors the CPU, spawns starter, which in turn spawns
your process - there are too many processes there, so another fork
should not matter that much.
You can try two things - starting your job only on the second CPU (
VirtualID=2 in requirements )
Another solution, though with a small chance to be helpful, is pinning
the process to CPU from perl. See the article:
On Fri, 2004-01-02 at 12:41, Ratul Mahajan wrote:
> i am unable to simultaneously use both CPU on my machines (intel/linux). my guess that this is a result of the nature of my jobs (see below). i'll appreciate if someone would verify my guess, and suggest a possible workaround.
> my job is a perl script that spawns another process using the "system" command. its quite likely that the spawned process will run on the second CPU. this "fools" condor into thinking that the new process is NonCondorLoad, with the result that the second CPU is never allocated (the first one is idle, since the original script is waiting for the spawned process to finish).
> is the above behavior expected with condor, or i am missing something? whats the best way to deal with it (run multiple virtual machines per CPU?)?
> -- ratul
> Condor Support Information:
> To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
> unsubscribe condor-users <your_email_address>
Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>