| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: OpenPandemics - COVID-19 Project
Thread: Invalid GPU work units |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 171
|
|
| Author |
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2179 Status: Offline Project Badges: 
|
Also on AMDGPU at least some all Invalid workunits:
workunit 814058990: OPNG_0085673_00096_4-- Arch Linux 728 Invalid 9/16/21 19:21:31 9/16/21 19:42:16 0.05 0.9 / 0.0workunit 813560316:OPNG_0085677_00112_4-- Linux Ubuntu 728 Invalid 9/16/21 10:43:10 9/16/21 10:55:18 0.06 0.9 / 0.0 |
||
|
|
biini
Senior Cruncher Finland Joined: Jan 25, 2007 Post Count: 334 Status: Offline Project Badges:
|
It seems that the invalid rates went up 15.9. I've had roughly 50 invalids daily.
----------------------------------------Btw, what's "Hainan" didnt know I have such a device in my arrrsenal :-D Result Name: OPNG_ 0085926_ 00423_ 1-- <core_client_version>7.16.11</core_client_version> <![CDATA[ <stderr_txt> projects/www.worldcommunitygrid.org/wcgrid_opng_autodockgpu_7.28_windows_x86_64__opencl_ati_102 -jobs OPNG_0085926_00423.job -input OPNG_0085926_00423.zip -seed 468273933 -wcgruns 900 -wcgdpf 18 INFO: Using gpu device from app init data 0 INFO:[04:35:54] Start AutoGrid... autogrid4: Successful Completion. INFO:[04:37:57] End AutoGrid... INFO:[04:37:57] Start AutoDock for OB3ZINC000010473908_2--7jji_001--ALYS417_inert.dpf(Job #0)... OpenCL device: Hainan INFO:[04:41:13] End AutoDock... INFO:[04:41:13] Start AutoDock for OB3ZINC000726820533--7jji_001--ALYS417_inert.dpf(Job #1)... OpenCL device: Hainan INFO:[04:43:45] End AutoDock... INFO:[04:43:46] Start AutoDock for OB3ZINC000105799901--7jji_001--ALYS417_inert.dpf(Job #2)... OpenCL device: Hainan INFO:[04:46:18] End AutoDock... INFO:[04:46:18] Start AutoDock for OB3ZINC000616319902_2--7jji_001--ALYS417_inert.dpf(Job #3)... OpenCL device: Hainan INFO:[04:52:42] End AutoDock... INFO:[04:52:42] Start AutoDock for OB3ZINC000505990098--7jji_001--ALYS417_inert.dpf(Job #4)... OpenCL device: Hainan INFO:[04:57:24] End AutoDock... INFO:[04:57:25] Start AutoDock for OB3ZINC000506010963--7jji_001--ALYS417_inert.dpf(Job #5)... OpenCL device: Hainan INFO:[05:00:59] End AutoDock... INFO:[05:00:59] Start AutoDock for OB3ZINC000505973495--7jji_001--ALYS417_inert.dpf(Job #6)... OpenCL device: Hainan INFO:[05:04:23] End AutoDock... INFO:[05:04:23] Start AutoDock for OB3ZINC000511884342--7jji_001--ALYS417_inert.dpf(Job #7)... OpenCL device: Hainan INFO:[05:08:59] End AutoDock... INFO:[05:09:00] Start AutoDock for OB3ZINC000616468912--7jji_001--ALYS417_inert.dpf(Job #8)... OpenCL device: Hainan INFO:[05:10:39] End AutoDock... INFO:[05:10:40] Start AutoDock for OB3ZINC000915473772--7jji_001--ALYS417_inert.dpf(Job #9)... OpenCL device: Hainan INFO:[05:13:56] End AutoDock... INFO:[05:13:56] Start AutoDock for OB3ZINC000010950953--7jji_001--ALYS417_inert.dpf(Job #10)... OpenCL device: Hainan INFO:[05:15:28] End AutoDock... INFO:[05:15:28] Start AutoDock for OB3ZINC001185676626--7jji_001--ALYS417_inert.dpf(Job #11)... OpenCL device: Hainan INFO:[05:17:57] End AutoDock... INFO:[05:17:57] Start AutoDock for OB3ZINC000516567185--7jji_001--ALYS417_inert.dpf(Job #12)... OpenCL device: Hainan INFO:[05:19:53] End AutoDock... INFO:[05:19:53] Start AutoDock for OB3ZINC000749303058--7jji_001--ALYS417_inert.dpf(Job #13)... OpenCL device: Hainan INFO:[05:22:48] End AutoDock... INFO:[05:22:48] Start AutoDock for OB3ZINC000728794827--7jji_001--ALYS417_inert.dpf(Job #14)... OpenCL device: Hainan INFO:[05:24:58] End AutoDock... INFO:[05:24:59] Start AutoDock for OB3ZINC000915720571--7jji_001--ALYS417_inert.dpf(Job #15)... OpenCL device: Hainan INFO:[05:27:11] End AutoDock... INFO:[05:27:11] Start AutoDock for OB3ZINC001167771109--7jji_001--ALYS417_inert.dpf(Job #16)... OpenCL device: Hainan INFO:[05:29:13] End AutoDock... INFO:[05:29:13] Start AutoDock for OB3ZINC000915533300--7jji_001--ALYS417_inert.dpf(Job #17)... OpenCL device: Hainan INFO:[05:31:23] End AutoDock... INFO:Cpu time = 179.750000 05:31:23 (10060): called boinc_finish(0) </stderr_txt> ]]> ---------------------------------------- [Edit 1 times, last edit by biini at Sep 17, 2021 6:30:24 AM] |
||
|
|
Biscotto
Cruncher Italy Joined: Apr 11, 2020 Post Count: 27 Status: Offline Project Badges: 
|
All my gpu tasks complete, then freeze my computer (doesnt happen when gpu calc is off) and then WCG says taks was server aborted, 0 pts. Is this happening to anyone?
----------------------------------------Papa Ryzen 5 3600 / Mama Radeon RX 560 |
||
|
|
erich56
Senior Cruncher Austria Joined: Feb 24, 2007 Post Count: 295 Status: Offline Project Badges: 
|
All my gpu tasks complete, then freeze my computer (doesnt happen when gpu calc is off) and then WCG says taks was server aborted, 0 pts. Is this happening to anyone? My hosts have many "invalid", some "too late", and very few "server aborted". Hopefully the problem will be solved soon! |
||
|
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2225 Status: Offline Project Badges: 
|
All my gpu tasks complete, then freeze my computer (doesnt happen when gpu calc is off) and then WCG says taks was server aborted, 0 pts. Is this happening to anyone? My hosts have many "invalid", some "too late", and very few "server aborted". Hopefully the problem will be solved soon! Same here. During my own downtime (sleep), I've had at least 30 "invalids", a few "Too late", and before i went to bed, I aborted some that already were at _3 or_4 when I got them. The batches sent out now, is wonky to say the least.... |
||
|
|
Biscotto
Cruncher Italy Joined: Apr 11, 2020 Post Count: 27 Status: Offline Project Badges:
|
All my gpu tasks complete, then freeze my computer (doesnt happen when gpu calc is off) and then WCG says taks was server aborted, 0 pts. Is this happening to anyone? My hosts have many "invalid", some "too late", and very few "server aborted". Hopefully the problem will be solved soon! Same here. During my own downtime (sleep), I've had at least 30 "invalids", a few "Too late", and before i went to bed, I aborted some that already were at _3 or_4 when I got them. The batches sent out now, is wonky to say the least.... Glad to know im not the only one. I wonder why it says server aborted tho... Papa Ryzen 5 3600 / Mama Radeon RX 560 |
||
|
|
erich56
Senior Cruncher Austria Joined: Feb 24, 2007 Post Count: 295 Status: Offline Project Badges:
|
... I wonder ... What I am wondering is that the project people did not notice yet that there is a major problem. |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
erich56: What I am wondering is that the project people did not notice yet that there is a major problem. It's been the weekend, and the caretaker staff may not be familiar with the system. About 40% of OPNG WUs dated 9/19/21 here have been marked Invalid so far  "Too late" status happens if you return a WU that you had already started at the time the servers declared the WU to be faulty due to the number of of errors/invalids among the wingmen reaching the allowed quota (I think). [Edit 1 times, last edit by Rickjb at Sep 20, 2021 2:07:23 AM] |
||
|
|
erich56
Senior Cruncher Austria Joined: Feb 24, 2007 Post Count: 295 Status: Offline Project Badges:
|
erich56: What I am wondering is that the project people did not notice yet that there is a major problem. It's been the weekend, and the caretaker staff may not be familiar with the system. hm, I would have assumed that with this kind of project, the technicians would not have a Monday thru Friday workweek :-( |
||
|
|
MStenholm
Advanced Cruncher Denmark Joined: Jan 7, 2010 Post Count: 97 Status: Offline Project Badges: 
|
10 pages of Invalid from two GPUs. That is around half of the Valid I normally produce.
---------------------------------------- |
||
|
|
|