RE: [Condor-users] Is VirtualMemory updated at intervals?

["Ian Chesal" <ICHESAL@xxxxxxxxxx>]

Resending this, but this time I'm compressing vmtracker.out so it makes
it past the max post size limit.

- Ian

> Man! I'll my machines are reporting LastHeardFrom around 
> 1105117918 seconds! Is that seconds from epoch maybe? That 
> might make more sense. I've only had the cluster running for 
> a few months, not umm...35 years. The LastHeardFrom and 
> EnteredCurrentState and EnteredCurrentActivity are pretty 
> close to each other so I'm getting updates as job state is changing.
> 
> I ran a monitor last night and dumped out the output from:
> 
> condor_status -f "%s\t" JobId -f "%s\t" Name -f "%s\t" 
> RemoteUser -f "%s\t" Acti vity -f "%d\t" VirtualMemory -f 
> "%d\n" ImageSize -const 'State=="Claimed"'
> 
> every five minutes.
> 
> The available virtual memory never moves for any of the 
> machines running jobs. It's always fixed at the total amount 
> of virtual memory for the machine. And I've got some big jobs 
> in there. 1GB++ in memory consumption. I've attached 
> vmtracker.out so you can see for yourselves. I would have 
> expected this number to dip by more than a little as two 
> 1GB++ jobs churned away on a machine.
> 
> - Ian
> 
> > -----Original Message-----
> > From: condor-users-bounces@xxxxxxxxxxx 
> > [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Jeff Weber
> > Sent: January 7, 2005 11:23 AM
> > To: Condor-Users Mail List
> > Subject: RE: [Condor-users] Is VirtualMemory updated at intervals?
> > 
> > Ian.
> > 
> > Dynamic.
> > 
> > Monitor the LastHeardFrom attribute for this machine from the
> > 	"condor_status -l"
> > command output and verify you are indeed receiving fresh 
> machineAds. 
> > The time unit is seconds.
> > 
> > 	Jeff
> > 
> > On Thu, 2005-01-06 at 19:20, Ian Chesal wrote:
> > > I really want to believe you but this goes against my
> > observations. My
> > > machines are constantly reporting the full amount of VM 
> for the box 
> > > regardless of what's running on them. And I'm running so
> > very memory
> > > intensive apps. Not so much as a twitch in the amount of VM
> > reported
> > > by the vm's on the box. Is it clipped for the Win32 version
> > of condor?
> > > 
> > > - Ian
> > > 
> > > > virtual memory is dynamically updated by the startd.
> > > > 
> > > > 	Jeff
> > > > 	Condor Team
> > > > 
> > > > On Tue, 2005-01-04 at 17:21, Ian Chesal wrote:
> > > > > I don't suppose someone from the Condor team could 
> ring on this 
> > > > > question? I haven't heard from any one...
> > > > > 
> > > > > Thanks!
> > > > > 
> > > > > - Ian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: condor-users-bounces@xxxxxxxxxxx 
> > > > > > [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian 
> > > > > > Chesal
> > > > > > Sent: December 22, 2004 4:20 PM
> > > > > > To: Condor-Users Mail List
> > > > > > Subject: [Condor-users] Is VirtualMemory updated at 
> intervals?
> > > > > > 
> > > > > > Page 24 in section 2.5 of the 6.7.2 manual says that
> > > > VirtualMemory
> > > > > > is "The amount of currently available virtual memory" for
> > > > a machine. 
> > > > > > I'm running non-Condor processes that are, according to
> > > > my machine,
> > > > > > eating up just about all of the virtual memory on the
> > > > machine. But
> > > > > > when I do:
> > > > > > 
> > > > > > condor_status -f "%d\n" virtualmemory <machine>
> > > > > > 
> > > > > > I'm seeing the same number (about 1 GB) reported 
> despite the 
> > > > > > fact that the OS says there is not 1 GB of available virtual
> > > > memory. This
> > > > > > is 6.7.2 on Windows XP.
> > > > > > 
> > > > > > Is the VirtualMemory figure for a machine a static or
> > > > dynamic value?
> > > > > > That entry in the manual led me to believe it was
> > > > dynamically updated.
> > 
> > --
> > Jeff Weber
> > University of Wisconsin, Madison
> > 
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > 
>

Attachment: vmtracker.out.gz
Description: vmtracker.out.gz