The Server Status page does not reflect correct numbers in the Work Status portion at the upper right when compared to the Tasks by Application at the lower left. Tasks Unsent vs Tasks Ready to Send

Bill F

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Is there an issue with the servers?

The total credits for my account have not updated for at least two weeks- stuck at 23,112,797, despite the workstation continuously working on milkyway tasks the entire time.

When I look at the Server Status page, it says 5 users in the past 24 hours, down from 10 users last week. Is it really just myself and a handful of other people working on this project?

The Server Status page does not reflect correct numbers in the Work Status portion at the upper right when compared to the Tasks by Application at the lower left. Tasks Unsent vs Tasks Ready to Send

Bill F

The standard Server Status page caches the information used to display the Tasks by Application section to reduce the amount of database activity needed -- it won't refresh for aboujt an hour, after which it refreshes the next time someone accesses the page!

I think it used to refresh the Work Status part of the page separately, but the PHP I found on GitHub seems to cache that as well, so I'm [now] at a loss to explain the discrepancy...

The Work Status part of the page only does simple counts against the results table with the various result status codes, which is a lot easier so not cached!

Cheers - Al.

[Edited after a re-check on the recent PHP sources...]

The Server Status page does not reflect correct numbers in the Work Status portion at the upper right when compared to the Tasks by Application at the lower left. Tasks Unsent vs Tasks Ready to Send

Bill F

The standard Server Status page caches the information used to display the Tasks by Application section to reduce the amount of database activity needed -- it won't refresh for aboujt an hour, after which it refreshes the next time someone accesses the page!

I think it used to refresh the Work Status part of the page separately, but the PHP I found on GitHub seems to cache that as well, so I'm [now] at a loss to explain the discrepancy...

The Work Status part of the page only does simple counts against the results table with the various result status codes, which is a lot easier so not cached!

Cheers - Al.

[Edited after a re-check on the recent PHP sources...]

One kink in that is you have to look at the Server version MW is using, I think they are an older version due to all the tweaks they have to make everytime a new version comes out.

wayne wrote:

Is there an issue with the servers?

The total credits for my account have not updated for at least two weeks- stuck at 23,112,797, despite the workstation continuously working on milkyway tasks the entire time.

When I look at the Server Status page, it says 5 users in the past 24 hours, down from 10 users last week. Is it really just myself and a handful of other people working on this project?

There is not really a problem, other than that the server currently has a lot of tasks queued which are each the first task of a workunit. (That is, tasks whose ID ends with "_0".) We need to finish practically all of these tasks before the server will send second (and if necessary third…) tasks of these workunits. (That is, tasks with "_1" IDs and higher.) Credits will be given when our hosts start to return "_1" results again. This is discussed in a few other threads already, e.g. "Number Crunching : Tasks Completed, but validation tasks remain Unsent".

The "active users" count on the server status page is merely the number of users which recently got credit, not the number of users which are fetching work/ computing work/ returning results.