What's the difference between performed_at and finished_at?

[francois]

Hi all! Here's a sample from our database:

        scheduled_at        |        finished_at         |        performed_at
----------------------------+----------------------------+----------------------------
 2025-05-05 17:03:02.134838 | 2025-05-05 17:03:02.319464 | 2025-05-05 17:03:02.167881
 2025-05-06 01:10:27.320281 | 2025-05-06 01:10:27.647867 | 2025-05-06 01:10:27.635975
 2025-05-04 22:21:38.899094 | 2025-05-04 22:21:38.929395 | 2025-05-04 22:21:38.909302
 2025-05-05 20:07:08.607535 | 2025-05-05 20:07:08.697185 | 2025-05-05 20:07:08.662565
 2025-05-08 03:10:19.906123 | 2025-05-08 03:10:21.520753 | 2025-05-08 03:10:21.51025
 2025-05-08 04:19:10.381516 | 2025-05-08 04:19:11.400598 | 2025-05-08 04:19:10.391567

All rows have a performed_at just a tad a couple milliseconds later than finished_at. I'm guessing that ActiveJob has a different meaning for both and GoodJob has to cater to that? What is the real difference between both?

Thanks!
François

[bensheldon]

• scheduled_at: when the job is expected to perform
• performed_at: when the job started performing
• finished_at: when the job ended performing

Calculations should be:

• performed_at - scheduled_at: queue latency
• finished_at - performed_at: execution latency
• finished_at - scheduled_at: total latency

Looking at your table, I think that's correct, you just have performed_at as the rightmost column when left-to-right in order it should be in the middle.