[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [condor-users] One vm or two?
Doesn't Condor update the job's Image size during the job is running? We
had our Matlab jobs evicted when they were reaching 1/2 of the memory
in the dual CPU machine. So the fact the job declares about itself to
require only 1 KB of RAM helps only to get the resource, but not get the
I'm definitely missing something, can you explain?
On Fri, 2003-12-05 at 16:39, Alain Roy wrote:
> >Thanks for the good advice. There are some useful tricks in there.
> >Unfortunately, though, I don't think it'll do what I need. When I say
> >"big" or "small" jobs, I mean that in terms of memory use, not running
> >time. Creating three equal vms would mean that each has one-third of
> >the machine's physical memory, and then no job that requires more than
> >that would ever run. Do I have that right? Or is it possible to assign
> >each vm all of the memory, and then use some other strategy to make them
> >share it?
> Each VM advertises that it has a certain amount of memory, but the virtual
> machine does not normally enforce that you only use that much memory.
> (Though you could set it up that way.)
> When your jobs run, you can set the requirements to lie about the memory
> usage. Your big jobs can say:
> Requirements = Memory > 1
> Normally Condor fills in this memory requirement, but it will not override
> what you write.
> Assuming you don't actually overrun the total free memory on a machine,
> this may work well for you.
> To ensure that users don't get it wrong, you may want to make a wrapper for
> condor_submit to help your users submit jobs in a consistent way. That's
> what was done in the document I shared earlier.
> 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>