-
Here ya go. I got this on another thread floating around here...
Changelog:
Quote:
- Fixes bug where updates cycle when not all locations update within 60 seconds
- More information added to event log on update failure
And further note from the developer posted in the beta forum.
Quote:
The old logic was as follows:
BerryWeather started an auto-update of all locations as soon as any of the locations' update time was older than the current auto update interval.
Testing if a location is out-dated was done every 60 seconds.
The problem with this was if one of the last locations was outdated an auto-update was triggered. If the auto-update did not finish within 60 seconds BerryWeather would check all locations again and still see the last locations being outdated. This would trigger another auto-update cycle...
The difference in the new build:
An auto-update will not be triggered if the last auto-update or manual 'Update All' is less than 'auto-interval seconds' ago.
I think this matches expected behavior: All locations will be auto-updated if only one location is out-dated at any time.
This is what caused some massive battery drain on some devices. If there was a network problem or an issue with the weather station that was reporting, it would timeout. Since there was still old data, it would try to update again. This led to an extremely heavy load on the servers, which led to some failed updates, which led to more load on the servers, which...well, you get the picture. This build fixes it. It will only cycle through once per update interval instead of trying to update continuously. Since I've had the beta of this, I have only had one failed update, and its because the weather station went down...12-17-09 10:59 AM - Thanks so much as always. Worth updating, it looks like. Ayayay, it will be the 3rd reboot today - during the outage, I thought my tour was causing it - rebooted twice LOL.Here ya go. I got this on another thread floating around here...
Changelog:
Quote:
- Fixes bug where updates cycle when not all locations update within 60 seconds
- More information added to event log on update failure
And further note from the developer posted in the beta forum.
Quote:
The old logic was as follows:
BerryWeather started an auto-update of all locations as soon as any of the locations' update time was older than the current auto update interval.
Testing if a location is out-dated was done every 60 seconds.
The problem with this was if one of the last locations was outdated an auto-update was triggered. If the auto-update did not finish within 60 seconds BerryWeather would check all locations again and still see the last locations being outdated. This would trigger another auto-update cycle...
The difference in the new build:
An auto-update will not be triggered if the last auto-update or manual 'Update All' is less than 'auto-interval seconds' ago.
I think this matches expected behavior: All locations will be auto-updated if only one location is out-dated at any time.
This is what caused some massive battery drain on some devices. If there was a network problem or an issue with the weather station that was reporting, it would timeout. Since there was still old data, it would try to update again. This led to an extremely heavy load on the servers, which led to some failed updates, which led to more load on the servers, which...well, you get the picture. This build fixes it. It will only cycle through once per update interval instead of trying to update continuously. Since I've had the beta of this, I have only had one failed update, and its because the weather station went down...12-17-09 01:53 PM
