[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-devel] Condor installation: VMMEMORY setting behaves odd / buggy?
- Date: Wed, 11 Aug 2010 19:50:17 -0700 (PDT)
- From: Rob <spamrefuse@xxxxxxxxx>
- Subject: [Condor-devel] Condor installation: VMMEMORY setting behaves odd / buggy?
Hi,
I'm about to install Condor on 300+ public library Windows PCs,
which have VMware 1.0.10 installed.
During the Condor installation I have to decide the value of VMMEMORY
and VMMAXNUMBER
>From the manual:
VMMEMORY
an integer value that defines the maximum memory each VM run on the
target machine.
VMMAXNUMBER
an integer value that defines the number of VMs that can be run in parallel
on the target machine.
I want to run at most one VM per slot on a multi core PC, so I set
VMMAXNUMBER = NUMBER_OF_PROCESSORS
I then decided:
VMMEMORY = ( 50 * RAM ) / ( 100 * NUMBER_OF_PROCESSORS )
or, in other words all the slots together share equally half of the PC's total
RAM.
(I thought that VMMEMORY should not be too large, as the Windows OS
may still need some RAM, even though it is in idle state. Is that right?
Or am I too conservative here?)
For example: a dual core PC with 2GB of RAM will then assign 512 MB to each
slot as VMMEMORY. I've tried this on a test PC with such specs, and I see:
$ condor_status -vm
Name VMType Network State Activity LoadAv VMMe ActvtyTime VMNetworking
slot1@SP_1F_02 vmware nat,bridge Unclaimed Idle 0.930 512 0+00:00:04
slot2@SP_1F_02 vmware nat,bridge Unclaimed Idle 0.050 12 0+00:08:10
Total Owner Claimed Unclaimed Matched Preempting Backfill
INTEL/WINNT51 2 0 0 2 0 0 0
Total 2 0 0 2 0 0 0
$ condor_status -vm -l
MyType = "Machine"
TargetType = "Job"
VM_Type = "vmware"
VM_Memory = 512
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
VM_AvailNum = 10000
MyType = "Machine"
TargetType = "Job"
VM_Type = "vmware"
VM_Memory = 512
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
VM_AvailNum = 10000
So it seems that each slot on this PC can use 512 MB RAM.
===================================================
Now, when a virtual machine with "vm_memory = 500" runs on
one slot, I will get following:
$ condor_status -vm
Name VMType Network State Activity LoadAv VMMe ActvtyTime VMNetworking
slot1@SP_1F_02 vmware nat,bridge Claimed Busy 0.000 12 0+00:00:34
slot2@SP_1F_02 vmware nat,bridge Unclaimed Idle 0.010 12 0+00:08:57
Total Owner Claimed Unclaimed Matched Preempting Backfill
INTEL/WINNT51 2 0 1 1 0 0 0
Total 2 0 1 1 0 0 0
$ condor_status -vm -l
MyType = "Machine"
TargetType = "Job"
VM_Type = "vmware"
VM_Memory = 12
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
VM_AvailNum = 10000
MyType = "Machine"
TargetType = "Job"
VM_Type = "vmware"
VM_Memory = 12
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
VM_AvailNum = 10000
This is what confuses me:
the VM_Memory has reduced to 12 MB on BOTH slots!!
This means: the 512 MB assigned to each slot, is actually the TOTAL
memory the two slots can use TOGETHER.
This seems to be in conflict with the description in the manual of VMMEMORY,
which says that EACH virtual machine (= each slot?) can use the
specified memory.....
Is something buggy here?
Thank you!
Rob.