fix: run jobs at interval instead of specific time #127

New Issue

AtHeartEngineer · 2025-07-08T08:40:34-04:00

AtHeartEngineer commented

2025-07-08 08:40:34 -04:00

Originally created by @ItalyPaleAle on 5/29/2025

While this is helpful for all jobs, it's particularly useful for the analytics job, to avoid all instances to send the ping at the exact same time, and to make sure it's always about 24 hours away.

Additionally, runs all database cleanup jobs in a single transaction, to avoid contention when all cleanup jobs are started at the same time (since they'd be competing to lock the database, especially with SQLite).

*Originally created by @ItalyPaleAle on 5/29/2025* While this is helpful for all jobs, it's particularly useful for the analytics job, to avoid all instances to send the ping at the exact same time, and to make sure it's always about 24 hours away. Additionally, runs all database cleanup jobs in a single transaction, to avoid contention when all cleanup jobs are started at the same time (since they'd be competing to lock the database, especially with SQLite).

AtHeartEngineer closed this issue

2025-07-08 08:40:35 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pocket-id#127