I have a very basic set of select/insert/update queries that run at 1 minute intervals.
The job runs on extremely lightweight table and every minute processes approx the same amount of data.
It is the only service that interacts with the tables in question.
Within a 5 minute period the job runs in ~0.5 second on the first 4 iterations ( minutes 1,2,3,4,6,7,8,9,11,12,13 etc). However on the 5th iteration so at 05,10,15,20,25,30 etc the job goes from 0.5 second to 8-10seconds.
Every 5 minutes it appears to get caught in some sort of lock that I can't locate.
The code is exactly the same for each 1 minute iteration and the volume of data to be processed doesn't really change which suggests to me it is db side.
I have attached the log file where you can see the job at 09:59:00 in less than a second, 10:00:00 in 8 seconds and then 10:01:00 in less than a second again.
Any guidance or advice would be greatly appreciated.
Regards
Liam