6:33 am
May 11, 2017
I really like your example with 2 minutes space between feeds, although it want work because they usually finish slower. Anyway, overlapping is solved by sacrificing an increased pull time and delay where last feed is worst in terms of periodicity. Imagine if you have 100 feeds. How do you squeeze them in 60 minutes given the first example. With many feeds you will always get overlapping.
Anyway, my setup is like your first example with 3 minute increments. This is optimal to periodicity and overlapping. I plan to add more feeds and hope that server will bear the overlapping, hence running few feeds in the same time.
That's how PHP works. Any scheduler will do overlaps, because it doesn't work in real time like cron, for example. Cron works every second and executes your command in the exact time. PHP is just a script and it works only when someone (a human, an SE bot or cron) launches it.
So let's imagine you have 100 feeds and every feed set to be pulled in some exact time. But it won't work, because your script doesn't work most of that time. Say you have many feeds that should be pulled at 10:00, 10:12, 10:28, 11:03 etc. But your script was launched only twice at 9:45 and 11:20. What should it do with your feeds that have missed their scheduled time?
Most Users Ever Online: 541
Currently Online:
17 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2817
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1627
Posts: 8280
Newest Members:
igor.buzaev, jeremyboucher, lthompson2709, MAC, duty3canada, backlinkmoroccoAdministrators: CyberSEO: 3913