What would cause a large difference between a "job submit time" and "job start time" in publishing?

Forum|Forum|3 years ago
October 11, 2022
7 replies
1884 views

I spent a bit of time looking at detailed logs of publish jobs and comparing them to data that's available in Publishing Statistics from the WVS monitor. I can connect the dots to all the values in the statistics except for the "Job Submit time". I understand that's when the publishing was triggered (say through a check-in). What would cause for a large difference between it and "Job start"? Shouldn't that be pretty much instant?

Windchill Visualization

avillanueva

23-Emerald I

Hard to tell from that screen shot but jobs are submitted on check in correct. However, its a queue. If there are other jobs that are running, it will do those first before getting to the one shown. Was the queue empty at the time you checked in? Was there another job running?

D

Dobi

Author

17-Peridot

Yes, job is submitted on check in. The queue was mostly empty (I can look at another job to confirm).

In this case I have a Job Submit time of 17:18. The job doesn't start (Job Start time) until 20:35 - some 3 hours later and that's when it gets added to the queue. Once it is in the queue (Worker Start time) it'll sit there until there's an available worker. For this job, there was a worker available not long after (this was 3rd in the queue so it sat there some ~3 minutes before the download started).

I'm not sure why there is a 3 hour delay between job submit and job start. Wouldn't job submit send the job to an appropriate queue more or less right away?

HelesicPetr

22-Sapphire II

Hi @Dobi

Does the worker have a setting to be available in period time to do publish job ?

That can explain the delay.

Or the queues were stopped and someone start them.

Or Worker failed and were stopped and someone start it

PetrH

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.