| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Discovering Dengue Drugs - Together - Phase 2 Forum
Thread: CPU Time 15 minutes, Zero Percent! |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 57
|
|
| Author |
|
|
Jack007
Master Cruncher CANADA Joined: Feb 25, 2005 Post Count: 1604 Status: Offline Project Badges: 
|
Interesting that Q6600 @ 2.4Ghz bit. Got same, with 4 sim, after 15:50 hours CPU time it's indicating 33.5% progress or 47.5 hours... W7-64. Uh oh, I have Q6600 15.5 hours roughly 33, 34 % with only 32 bit... I just bought win 7 64 bit hoping it would help my speed... by chance did you update your BOINC to latest 64 bit? (I know it's you Sekerob, so I feel silly asking you that, but some people dont like latest versions)  |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Testing for you and all's benefit a 6.10 64 bit alpha client in production... and as said 4 simultaneous are running now. Fastest after 21:32 CPU hours on 46.16% or steady on target of 46.5 hours.
----------------------------------------As for the benefit, it varies per science, there being no general guideline. Does it harm when you get the 32 and 64 bit W7 disks for 1 price? What I do know is that W7 is so much more efficient that I'm actually getting more crunch time out of it, 11 minutes per core per day... more uptime, less going towards system housekeeping too. That's 45 minutes crunch time for me quad per 24 hours.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
bad workunit?: erlc_b153_ps0000 2 of us are already reporting it as "The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)" It is a work unit I am looking into. It is probably a bad work unit. -Uplinger |
||
|
|
Somervillejudson@netscape.net
Veteran Cruncher USA Joined: May 16, 2008 Post Count: 1065 Status: Offline Project Badges: 
|
I love when new projects come out as the energy level really increases. I recieved 2 WU's on my i7 3.33mHz but yet to start will need to finish up my HCMD II WU's first.
|
||
|
|
TBirdTheYuri
Advanced Cruncher France Joined: Mar 5, 2006 Post Count: 115 Status: Offline Project Badges:
|
New estimates this morning : TBird, it seems that you have given us estimates based on BOINC's estimated time to completion.i7 920 @ 3GHz : 8 units simultaneously - 50 hours per unit Q9450 @ 3GHz : 4 units simultaneously - 30 hours per unit Q6600 @ 2,4GHz : 4 unites simultaneously - 40 hours per unit T2050 @ 1.6 GHz : 2 simultaneous units - 100 hours per unit If you want to show more realistic times you can safely extrapolate from the work already done. Progress seems to be very linear. Personally I have one running in a Q6600 at 3.16 GHz and it should last between 39 and 40 hours (average 47 minutes between checkpoints - 2 %). To all: About the (normal) 0.000 % phase at the beginning note that the first checkpoint is taken at 2.000 %, therefore be patient. Cheers. Jean. That's what I did, estimates Boinc fanciful. I calculated from the time served and the percentage already done. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Looks like my 3 dddt2 WU will come in about 55 hours each on my AMD Phenom
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Are they going to try and gear these work units down to a 10 hour or less runtime or are they going to continue to be extremely long with huge memory consumption.
Just wondering if my other machines will ever be able to work on this project. Thanks, Faldor |
||
|
|
wplachy
Senior Cruncher Joined: Sep 4, 2007 Post Count: 423 Status: Offline |
bad workunit?: erlc_b153_ps0000 2 of us are already reporting it as "The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)" It is a work unit I am looking into. It is probably a bad work unit. -Uplinger Appears this one may have a problem as well: erlc_ e002_ ps0000_ 5-- - In Progress 2/18/10 17:32:23 2/24/10 07:56:23 0.00 0.0 / 0.0 erlc_ e002_ ps0000_ 4-- 612 Error 2/18/10 17:23:06 2/18/10 17:32:15 0.00 0.0 / 0.0 <---Mine erlc_ e002_ ps0000_ 3-- - In Progress 2/18/10 13:34:48 2/24/10 03:58:48 0.00 0.0 / 0.0 erlc_ e002_ ps0000_ 2-- 612 Error 2/18/10 09:51:59 2/18/10 17:23:02 0.00 0.0 / 0.0 erlc_ e002_ ps0000_ 1-- 612 Error 2/18/10 06:44:45 2/18/10 13:34:42 0.00 0.0 / 0.0 erlc_ e002_ ps0000_ 0-- 612 Error 2/18/10 06:44:44 2/18/10 09:50:57 0.00 0.0 / 0.0 All errors are The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)
Bill P
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sorry I should have read the news article first. :(
So type A are 30->100 hours, type B up to 10 hours and type C 1->5 hours. :) |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
wplachy,
I will look into that one as well. There are a handful of work units that error out immediately. Meaning with in the first 15 seconds. From what I know, there is an error in the ligand parameterisation which we are working on catching before the work units are sent out. -Uplinger |
||
|
|
|