[fixed] PRCG displayed on Recent CPUs page is not updated?

[fz4z]

Search for user on the " Recent CPUs page ( https://apps.foldingathome.org/cpu )" , the " Project, Run, Clone, Gen " displayed on the page is not updated ?
( Only the time of "Last returned" is updated )

08/25/2021 : This issue has been fixed.

[Neil-B]

This is a known "feature" which at some point will be corrected ... It "broke" a while back and with scarce resource focused on keeping the servers/clients/cores/projects running it is still in the queue to be resolved.

I'll also mentioned that the WU Status App also has a known "feature" You may also notice where the Returned and Credited column labels are switched ... again it is in the queue to be resolved.

[aetch]

It's a known broken page.

It's supposed to show a selection of work units you have completed over the last 90 days (3months). For someone like myself that could be thousands (1500+) but it shows a mere seven (7).
I'd also noticed an oddity where it gives you a CPUid, current IP address and a recent "Last Returned" date/time but the detail is all wrong.

Prime example
CPUid_____________IP Address_______Team____Slot________OS_________Last credit____Got bonus_Last returned_______Project_Run_Clone_Gen
F2239A5ED299F542__xxx.xxx.xxx.194_0________NVidia GPU_Windows____5,208.3_______1_________2021-08-24 13:54:38_16452__96__184___19

Current?___________current_________current__ok?________yes_________low for a gpu__yay_______today?_____________this is a CPU unit from January, I double checked with my logs

If you want detail on a specific work unit use the "WU Status" page -> https://apps.foldingathome.org/wu
If you want statistics on what you are producing I'd suggest extremeoverclocking.com, I believe this might be your stats page -> https://folding.extremeoverclocking.com ... &u=1210166

[Neil-B]

It is actually supposed to show the most recent wu for any specific CPUid ... if you run 7 slots it will shows seven lines ... but the data is currently borked - iirc the timestamp is correct but the rest is not

[Joe_H]

It's supposed to show a selection of work units you have completed over the last 90 days (3months). For someone like myself that could be thousands (1500+) but it shows a mere seven (7).

What it is supposed to show is the last WU returned by each specific "system" that processed them during that 90 days. A "system" will be on a specific computer and represents one folding slot configured on that computer. So if you have a computer with a CPU slot and 2 GPU slots there will be 3 separate lines. You will not get thousands reported except if you run thousands of separate folding slots.

Known issues at this point include that they supposedly reduced the look back time to less than 90 days but did not update the page itself. The bug on how the date/time fields for returned and credited are reversed has been mentioned, as has it not reporting recent WUs properly.

When this will be fixed I do not know. It is relatively low priority, and up until recently they only had one paid developer. He has been tasked with updating the server code to provide new features that have been requested. He is also bringing a recently hired developer up to speed on the codebase for a version 8 of the client. That had been started pre-COVID but put on hold due to keeping up with the COVID response.

[aetch]

[What it is supposed to show is the last WU returned by each specific "system" that processed them during that 90 days. A "system" will be on a specific computer and represents one folding slot configured on that computer. So if you have a computer with a CPU slot and 2 GPU slots there will be 3 separate lines. You will not get thousands reported except if you run thousands of separate folding slots.

Thank you, I've tried a few times to get a clear answer on what the page is supposed to show and none have been as clear as this.

I still think the page is borked.

[Neil-B]

... and as if by magic (or by awesome dev work tbh) the Recent CPUs "random data feature" is no more ... or to be more precise the issue with the sql has been addressed and the data shouyld now be updated properly with each wu returned - that means for any slot that returns a wu from now on the data should update for that slot - for slots that haven't returned a wu yet since the code was fixed the "random data feature" will continue to exist either until a wu is completed or iirc until the slot ages off after 90 days.

As with all feature advances the potential for further unexpected feature creation is possible so please report any surprises as/when/if you spot them

Kudos (and "Thanks") to dev who managed to track down the issue whilst juggling the many other tasks in the pipeline !!