Why did three separate python scripts using schedule start at different time eventually converged to be in sync? #614
Comments
fireattack
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is more of a question than bug report, but this phenomenon has been confusing me for years.
I guess a this is the appropriate place to ask about it.
So I have a script using
scheduleto check something periodically.It roughly looks like this (pseudo code):
I will typically run three or four of such scripts in parallel (so different Python processes) on my machine. Because I do it manually, they usually start at different time, a few seconds apart.
What I've noticed that if I let the scripts run for a while, say 1 hour or 2, I find that the current time they print at the start of each task eventually became the same.
For example, I parsed the logs from three instances and print the difference between three logs:
As you can see, at the beginning 2 is 6 seconds behind 1, and 3 is 4 seconds behind 2.
But after merely 1 hours, they become in sync. And they STAY in sync for the rest of the time.
I fully understand schedule isn't meant to have exact timing, so I never expect the interval to be consistent. But I don't understand why would three totally unrelated python processes would eventually converge together.
In the above script I only have timestamp in seconds in my log. But in fact, they are more in sync than that!
In the actual full script, part of the scheduled task is to call a external program (
subprocess.run) when the condition is met, which creates a folder calledfolder_{timestamp_in_ms}. And it has happens to me once, that two different running scripts create the folder at exactly same millisecond due to this convergence.I can't for the life of me figure it out. I hope someone can provide some insights. Thanks in advance.
The text was updated successfully, but these errors were encountered: