Just to give everyone a quick update on Beta:
Beta methods so far shows a good quality / usability, but alas I’ve run into an emerging problem with which I need to deal with. This problem is described in detail here (link), but in summary it has to do with the load a 3rd party cron-job server is putting on the wufyi server. Unfortunately it does not seem that cron-job.org will implement any changes anytime soon.
Many of you may have gotten an increasing number of email notifications about a 503 server error from your cron-job, this happens due to cron-job.org sending requests for processing in parallel during the first few seconds of every minute. This is particularly bad every 30 minutes (at the top of the hour, and 30 minutes later), when practically every schedule of choose coincides with each-other sending every single user to be processed within a few seconds of each-other.
Unfortunately, the data source(s) for beta have an unfortunate disadvantage over an official wunderground API: data for beta source takes, on average, 2 to 3 times longer to retrieve. I would be happy to roll out beta changes to the main wufyi branch, but I expect a drastic increase in 503 errors in case I use it as is.
It looks like beta period will have to be extended by up to a week as I implement / test the new method of scheduling / processing the data synchronization. Meanwhile new / existing users, should feel free to switch the cron-job URL to use the new beta.wufyi.com.
Alas I can’t yet upgrade everyone automatically to the new code due to an expected increase of 503 server issue notifications. Some of you will have to continue using API based wufyi code for now, I’ll try to make sure it will not be so for long.