morten.brekkevold@uninett.no said:
If you set DEBUG level logging for `nav.ipdevpoll.jobs.jobhandler_timings`
In case somebody reads this thread in the future: The variable is `nav.ipdevpoll.jobs.jobhandler-timings` (with '-')
It seems like typical values are like these (looks like I will earn nothing by moving statmulticast to 5minstats):
2017-02-24 12:59:31,914 [27044] [DEBUG jobs.jobhandler-timings] [1minstats bodo-gsw.infra.uit.no] Job '1minstats' timings for bodo-gsw.infra.uit.no: StatSystem : 0:00:10.781017 StatMulticast: 0:00:00.000089 ----------------------------- Plugin total : 0:00:10.781106 ----------------------------- Job total : 0:00:11.034561 Job overhead : 0:00:00.253455 2017-02-24 12:59:31,915 [27044] [INFO schedule.netboxjobscheduler] [1minstats bodo-gsw.infra.uit.no] 1minstats for bodo-gsw.infra.uit.no completed in 0:00:11.036677. next run in 0:00:48.963349.
But interesting things are happening. A lot of jobs have overhead-values in the 0:00:00.X range like the example above, but then suddenly a bulk of jobs have overhead values up to 10 seconds!
Looking forward to 4.7
--Ingeborg