Re: [HTCondor-users] RemoteWallClockTime vs CommittedTime

["Todd Tannenbaum" <tannenba@xxxxxxxxxxx>]

Cpu time could exceed wall clock time if the job is using multiple cores (via multiple threads or processes), which is always a possibility unless you configured htcondor to enforce cpu limits on a slot via either cpu affinity knobs or by enabling cgroups...

-- Sent from my HP Veer mobile phone

---

On Oct 15, 2013 8:44 AM, John Weigand <weigand@xxxxxxxx> wrote:

We have noticed a problem in collecting accounting data from the HTCondor
classads.  We are seeing situations where CPU is exceeding Wall time.

We use the RemoteWallClockTime classad as the basis of Wall time.  According
to the documentation, this appears to be the correct one to use.  The accounting
system also captures CommittedTime.   We are seeing conditions where
CommittedTime exceeds RemoteWallClockTime.  One of many cases....
  CommittedTime = 3944     RemoteWallClockTime = 1   Total CPU = 1935

Based on the documentation, if I am interpreting it correctly, CommittedTime
should never exceed RemoteWallClockTime since CommittedTime can get reset to
zero if evicted w/o a checkpoint.  And RemoteWallClockTime does not.

I am trying to understand under what conditions this can occur.
It is making no sense to us.

Thanks
John Weigand
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/