| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: this is a really long work unit |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 149
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
faah5012_1hvl_1hsh_00_0 running for 15 hours with another 16:22 to go.
Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz [x86 Family 6 Model 15 Stepping 11] Processor features: fpu tsc pae nx sse sse2 mmx Microsoft Windows XP: Professional Edition, Service Pack 2, (05.01.2600.00) Memory: 2.97 GB physical, 3.60 GB virtual Disk: 74.52 GB total, 48.83 GB free |
||
|
|
archiea.george@gmail.com
Cruncher Joined: Jul 3, 2008 Post Count: 15 Status: Offline Project Badges: 
|
faah5008_1fiv_1aaq_00_1 has been running 22:42:35 and has 7:43:08 to go on my iMac
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sekerob,
I think you are correct... I just got faah5010_6fiv_1fiv_00_2 It's been running now for a little more than 2 1/2 hrs and indicates it's only 10% complete... yet the total time to completion indicates its only going to take 8 hrs. We'll see!  Thanks for the pointer. I'll have to wait and see if I can ever see what the other machine had to do to compute it. This will be interesting I'm sure. |
||
|
|
mikaado
Cruncher Joined: Dec 3, 2007 Post Count: 14 Status: Offline |
Oh boy... these new faah wu's are getting bigger and bigger... A few days ago I had a work unit that took my e4400 @ 2,0GHz about 19 hours to process (250 points). Now I have these units
faah5008_1pro_1a9m_00_1 faah5008_1hpx_1a9m_00_0 that I have been crunching for more than 6 hours and they show over 19 hours of work is still left. This is not a problem for me, but I think someone with an older machine may want to cancel these WU's. |
||
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges: 
|
Hi Guys,
----------------------------------------I've got these 4 running:- Work Unit Est. Credit Est. Points CPU faah5008_1hvl_1ajx_01_1 1654 11580 Athlon MP 2000+ faah5010_1bv9_1g2k_00_1 832 5830 Athlon 64 X2 4200+ faah5014_1mtr_1met_00_1 840 5884 Phenom 9600 faah5017_1hiv_9hvp_00_1 987 6910 Phenom 9600 The estimates are taken from BOINCView numbers, which seem more accurate than BOINC Manager. The first job has used 21 hours CPU and is at 11.66%, that's about 180 CPU hours!! Pete PS - Sorry about table format  "Patience is a virtue", I can't wait to learn it! |
||
|
|
E165852
Cruncher Joined: Jul 17, 2008 Post Count: 4 Status: Offline |
Bingo!
I have hit faah5012_1b6j_1hsh_00. It consumes 29.5 hours of CPU power of my ThinkPad T61 with Intel T7700 2.40 GHz processor for bit less than 85% of work unit. I am expecting to complete this work unit before I leave my home to the office tomorrow morning. This is the first time I've got such a big transaction. BTW, I want to request the transaction programmer not creating this big of transaction any more. I could contribute only 2 or 3 transaction per day during this period. Thanks. |
|||
|
||||
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Hello,
I have looked into the work unit details as to why the estimation script is off by so much. It appears that one of the parameters in the grid file was not taken into effect during the estimation. This number has usually been static in the past thus was not part of the equation. On a side note, these work units from 4998 - 5017 are of interest to the researchers and need to be finished before the code switch to single redundancy. I had thought these would be quick running batches due to the number of work units in each batch. At this time, I have suggested that we push through these very large work units so the switch to single redundancy can be made and we can get back to doing normal work units. Also, if the members don't cancel the work units the researchers will get their results back sooner. Please let these work units run to the end as they are important. Also, we are looking into extending the deadlines for these work units. Again, I am sorry that these work units are running longer than usual. Please be patient with them as they are not the normal work units that run through the grid. -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Uplinger,
Would it be a good thing if you could find a way to schedule these extra large WU's only to systems that are running fairly quick CPU speeds? No sense in distributing these kinds of work loads to systems that require several days to process. My WU faah5010_6fiv_1fiv_00_2 is running on my 3.4Ghz Q66. As I type this the Bionic Client is indicating that it has run for 5 1/2 hrs; is 22% complete and indicates another 6 1/2 hrs until completion. wadaya think, or is this in the same vein as what the rice project is doing with running for some specified period of time then quitting? |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Barney,
----------------------------------------These work units are not limited by time like the RICE project. Also, all of these work units have been sent out already. Due to the small number of work units in a batch these went out quicker than the normal sized batches. Also, the variable that was the main cause the estimation script *being* off by so much allows the researchers to get back higher quality results due to this. -Uplinger [Edit 1 times, last edit by uplinger at Jul 31, 2008 3:49:06 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
uplinger,
----------------------------------------Thanks for the explanation.... I just love it when a perfectly good plan falls apart at the seams!  [Edit 2 times, last edit by Former Member at Jul 31, 2008 4:15:42 PM] |
||
|
|
|