The info displayed in the stats page is not correctly updated.

For example, my team's Total Credit is not the correct (it's missing about 100000 credits) and more strangely is that the value of the total credit between pages of the team members stats is diferent.

By the time I posted this it was (with the browser's cache cleaned):

1) .. 20) 697801.31
21) .. 40) 698032.42
41) .. 60) 697673.09
61) .. 80) 697673.09
81) .. 100) 697673.09
101) .. 120) 697673.09
121) .. 127) 697673.09

Has anybody experienced the same problem?

---

The team credit is figured independently of the users credit and credit is only granted to the team for work done while on that team. So the total of the users credit will never match the teams credit.

I would expect the reason the numbers changed when changing pages is that they are actually live and some of the team's work was validated while you were changing pages.

---

BOINC WIKI

BOINCing since 2002/12/8

I don't understnad why they didn't manage to sort the members by credit corectly.

---

WARR - Wissenschaftliche Arbeitsgemeinschaft für Raketentechnik und Raumfahrt
(WARR - scientific working group for rocket technology and space travel)

> I don't understnad why they didn't manage to sort the members by credit
> corectly.

That is why they give us XML - so we can do it better :) They turned off most webpage sorting features to decrease database load and it is obvious that pretty website features aren't very high on their priority list (understandably). So they let 3rd party sites deal with it.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

> > I don't understnad why they didn't manage to sort the members by credit
> > corectly.

Actually the stat pages here at seti were disabled for a long time untill the caching functions were added. Not to load the system too much has much higher priority than being able to view live stats (as you could initially) or sort them.

The problem John, is that it increased and then decreased to a value lower than the first one.

697801.31 -> 698032.42 -> 697673.09

And if you return to any of the pages the values are always the same, ie not updated.

That's a little bit strange, no?


> I would expect the reason the numbers changed when changing pages is that they
> are actually live and some of the team's work was validated while you were
> changing pages.
>

---

> The problem John, is that it increased and then decreased to a value lower
> than the first one.
>
> 697801.31 -> 698032.42 -> 697673.09
>
> And if you return to any of the pages the values are always the same, ie not
> updated.
>
> That's a little bit strange, no?
>
>
Did somebody leave your team?

---

The values were taken with one or two seconds of diference so the total credit should always be the same between pages. I think.

> > The problem John, is that it increased and then decreased to a value
> lower
> > than the first one.
> >
> > 697801.31 -> 698032.42 -> 697673.09
> >
> > And if you return to any of the pages the values are always the same, ie
> not
> > updated.
> >
> > That's a little bit strange, no?
> >
> >
> Did somebody leave your team?
>

---

It must be a miscalculation of some sort.

I just took Toby's team for example and the values in pages 1 .. 4 are:

3075307.60 -> 3075357.44 -> 3077354.00 -> 3077354.00

---

> The problem John, is that it increased and then decreased to a value lower
> than the first one.
>
> 697801.31 -> 698032.42 -> 697673.09
>
> And if you return to any of the pages the values are always the same, ie not
> updated.
>
> That's a little bit strange, no?
>
>

To both speed things up & not access the database all the time, the web-server is caching the pages that is possible to cache. This means, if user1 example checks the top-20-team-listing, the info must be generated from the database. But if user2 comes 5 seconds later and also checks the top-20-team-listing, he gets the cached copy instead and therefore doesn't access the database at all.

Since the pages is probably not generated and cached before needed, this is probably the reason for slightly different score showing up on different pages.

As for how long the cached copy is used before re-generated from database, no idea, but according to the stats-page Berkeley is updating the stats every 12 hours.

The stats-dumps is getting updated every 24 hours.

> As for how long the cached copy is used before re-generated from database, no
> idea, but according to the stats-page Berkeley is updating the stats every 12
> hours.

Default BOINC settings are to update at most every hour. I don't know if the seti project tweaked these settings to 12 hours instead to save the servers a bit.