WUs not analyzed
Message boards :
Number crunching :
WUs not analyzed
Message board moderation
Previous · 1 · 2
| Author | Message |
|---|---|
 [SG-FC] dingdong   Send message Joined: 14 Apr 10 Posts: 16 Credit: 2,137,851 RAC: 484 |
Thank you very much for repairing IT! |
    Send message Joined: 20 May 10 Posts: 552 Credit: 1,900,227 RAC: 789 |
Mine are back as well WOO HOO!!! |
    Send message Joined: 29 Jul 11 Posts: 334 Credit: 1,239,573 RAC: 322 |
Hopefully there's no other database problems because it appears the hours are still backfilling. My total hours so far today are slightly more than real CPU hours. Yesterday, I had nearly 2.5 times a normal days real CPU hours. |
|
Send message Joined: 20 May 10 Posts: 552 Credit: 1,900,227 RAC: 789 |
Hopefully there's no other database problems because it appears the hours are still backfilling. My total hours so far today are slightly more than real CPU hours. Mine did the same thing |
 Send message Joined: 4 Apr 23 Posts: 2 Credit: 42,584 RAC: 47 |
A similar miss-count is potentially being applied to Primegrid GFN-15 for cpu only tasks. Primegrid restarted the GFN-15 cpu only tasks on 4-10-23. It has been two days of trying to compare the values WUprop applies vs the machine hours. On average each of the tasks is 8 minutes. This means my machine calculates 7 work units per hour. WUprop units take one hour to compute. WUprop is counting an hour of machine time as 0.2 running hours. As a comparison GFN-16 takes 48-50 min per work unit. WUprop presents this as the same value in running hours. Have other machines experienced this and is there a fix to this running hour difference ? |
Landjunge   Send message Joined: 28 Feb 13 Posts: 4 Credit: 5,837,549 RAC: 1,554 |
For me GFN-15 CPU Tasks are not couting too. =( |
©2024 Sébastien