Hi,

as the new bug reporting system does not allow any more replies, I do post my reply to the answer for bug 33 here.
I knew there are different update runs on the server and that the different times of those updates can cause those discrepancies in the output. And I know that it is not trivial to get the information from all updates to be in sync, as I have done a stats tracking system covering 18 different DC projects myself in the past. And I didn't even want to propose that you make all tables be synced.
But I'm a bit confused why you don't just fix that in the page output (at least for the world position record thingy). Even if those 2 numbers come from different tables, you do have them both when the output of the page is generated and you can easily compare them to detect and (lazily) fix the discrepancy in the output.
Or do I make wrong assumptions about your architecture, system and/or server? If so, I'm really sorry for bothering you with this again.

Ciao, Michael.

In my view, only the numbers of the daily update matter for the history tables. Durning the day, many updates run, on different projects. These influence the current-position and current-credit only, and nothing else.

All other calculations (highest ever, history, credit/day etc) are calculated only once a day, based on 24hours from all projects.

I could calculate highest ever on every update (every 30 minutes) but :

a.) I think this is not correct as this value won't be found in your history, which results in more bug reports (my highest ever isn't found in my history, what's wrong?)
b.) Doing more calculations would mean longer updates. The incremental update should complete as fast as possible. At the moment an incremental update finishes in 15~30 minutes, daily update takes 1,5~2 hours.