The script runs exactly 60 minutes after the last user's results are cached. This can take up to a minute or two to run all of them, and your cached file may not be generated in the same order as it was last time -- which is why your updates appear not exactly 60 minutes. If it jumps by something like 5 minutes, it's probably because the first attempt at caching the files timed out -- it's a pretty cpu-intensive operation, and that's why we went to the hourly caching anway. As aelith said, the comments are still real-time.
Drew |
