| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Another curiouce resuts for FAHV_x3VQ |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
One of my rigs runs 2 instances of BOINC.
Config is : CORE i7 3770 w/HT on. 16GB RAM and Win7 pro. I run VMWare on it with 4 virtual CPU and 6GB RAM assigned Running Ubuntu 12.04 + BOINC 7.0.27(Ubuntu1264). . Beside the VM, a Windows virsion of BOINC 7.2.42(HOME04) running with 50% of CPU assigned. Today, I found following results. FAHV_ x3VQE_ A_ IN_ LEDGFb_ rig_ 0224673_ 0018_ 0-- Ubunyu1264 Valid 14/09/16 12:33:28 14/09/19 20:44:29 19.08 / 20.30 64.7 / 64.7 FAHV_ x3VQD_ IN_ LEDGFb_ rig_ 0223729_ 0033_ 0-- HOME04 Valid 14/09/15 21:40:34 14/09/19 18:43:57 32.59 / 39.13 64.7 / 64.7 FAHV_ x3VQD_ IN_ LEDGFb_ rig_ 0223722_ 0036_ 0-- HOME04 Valid 14/09/15 21:40:34 14/09/19 14:19:14 32.62 / 39.61 64.7 / 64.7 FAHV_ x3VQD_ IN_ LEDGFb_ rig_ 0223722_ 0027_ 0-- Ubunyu1264 Valid 14/09/15 21:39:56 14/09/19 17:52:50 23.66 / 25.09 64.7 / 64.7 As shown above, all has claimed 64.7 point regardless of the runtime. There are more such WUs on this H/W. Can sombody explain why this happening? Usually, FAHVs complete about 4h on the Linux under VM and 6h on Win7. this 64.7 point issue only occures for the long run WUs |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
These are all FAHV units which have been sized incorrectly. The length of time they should justify many more points, but have run afoul of the maximum point number which is in place to discourage or prevent cheating. Basically I think there is a maximum number of points which may be granted to a work unit (somewhere in the 600 to 700 BOINC points range - I think). Even though you are not cheating, the length of the work units entitles the work unit to more points than the maximum and it will therefore revert to the default "cheat" number. I have had several of these also, on a machine which normally gets 30+ points per hour, I was shoved back to about 2.5 points per hour. Per a post by Seippel, (https://secure.worldcommunitygrid.org/forums/...ad,37163_offset,50#469407) the techs have fixed the issue and the re-sized units should be flowing in a day or two. The issue has been frustrating, but in the big scheme of things, no big deal.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
|