On Mon, Oct 26, 2015 at 5:43 PM, Jesse Becker <becke...@mail.nih.gov> wrote:
> On Mon, Oct 26, 2015 at 02:22:19PM -0700, Skylar Thompson wrote: > >> Hi Mark, >> >> IIRC maxvmem is a sampled value, so if the job experiences rapid >> fluctuations in vmem usage, it might not be entirely accurate. >> > > As you said, vmem is a polled value, and will change over time. > However, maxvmem should be a strictly non-decreasing value. > Thanks to both of you. This is good to know, but disappointing. If we get motivated enough I'll see if I can find in the source where the polling interval is coded and try decreasing it. If it is that straight forward, I have no idea. > > There were some versions of SGE (et al) where the vmem reporting was > invalid above 4G of RAM becuase a 32bit int was used for tracking this > value. I believe that all *current* versions of SGE derivatives (open > source and commercial) have this fixed. The low reporting I'm seeing is with value much less than 4G, so it's probably not this issue. -M
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
