F*#$§&g hell, that's a lot. OK, so no WUProp data from my GPU for another 400hTrotador hat geschrieben:Well, don't be in a hurry to update, 465 hours so far...Sänger hat geschrieben:Mine is this: cms_GA[e30-50MB_Lin64f]_Oryza-sativa-Indica-Group_CM000129.lin.EMBL_RF00028_Intron_gpI_1298201813_4_16, i.e. #17 of that WU. I'm still a bit away from the deadline (29th it is), but can you tell me the crunch time 'til now? I want to update my BOINC, but can't until that monster is done
Finally the first one finished, only 670 hTrotador hat geschrieben:Hi,
This one is reaching its deadline but it's still running (at 100%):
cms_GA[e30-50MB_Lin64f]_Oryza-sativa-Indica-Group_CM000129.lin.EMBL_RF00028_Intron_gpI_1298201813_4_3
I have another one that looks like it will also need more time, at 100% for long time :
cms_GA[e30-50MB_Lin64f]_Oryza-sativa-Indica-Group_CM000131.lin.EMBL_RF00028_Intron_gpI_1298201813_5_4
Could you extend the deadlines for both units?
Thanks
but it appears with the "completed can`t validate" label, Is it because is late to the original deadline? No wingmen has finished this unit yet.
Answer:Trotador hat geschrieben:...but it appears with the "completed can`t validate" label, Is it because is late to the original deadline?
..and that is why it cannot yet (!) be validated.Trotador hat geschrieben:No wingmen has finished this unit yet.
I've had a couple of power failures but since I'm running it on my laptop the unit never stopped. I wish there was a way to find out how much longer! Please provide a URL to that specific WU and your machine, so that we can have a look at the situation. Generally, it is normal for the Intron_gpI WUs to really run VERY long, i.e. up to 1200 hrs. But exact runtimes of course depend on exact specs of the WU. Unfortunately, the runtime prediction routine fails for these Intron_gpI WUs, so the progress bar is not helpful at all. You can check in your taskmanager for progressing CPU runtime of that CMSEARCH task and also post the maximum memory usage consumed so far.[B^S] Dragonstar hat geschrieben:Right now I'm at 750 hours (100% for the last month) and still crunching
My deadline is April 13th and was wondering how much longer it's going to take? I see one person completed unit in ~32,000 secs but I've seen one other aborted at over 2 million secs
Not with the current version of CMSEARCH.[B^S] Dragonstar hat geschrieben:Also, if I finish other workunits on this laptop and free up the cores will this monster unit use the free cores to finish faster?
The relevant machine ID is 169 and that WU now has run for 306 hrs with a peak RAM consumption of 1.9 GB. It continuously uses 900 MB of RAM. I have a second of that kind running in parallel on the same machine and normally these finish without problems unless someone shuts that machine down. 
So far I'm at 824 hours with peak RAM at 1.92 GB and 1.03 GB continuous RAM according to my task manager.Michael H.W. Weber hat geschrieben:Well, I am currently working on the same WU.
From what I can see your machine should be capable of completing it successfully, just make sure you do not encounter a power failure or system shut-down and prepare for maybe 1200 hrs of runtime.
Michael.
OK, you did it in 670h, congratz for thatTrotador hat geschrieben:Well, don't be in a hurry to update, 465 hours so far...Sänger hat geschrieben:Mine is this: cms_GA[e30-50MB_Lin64f]_Oryza-sativa-Indica-Group_CM000129.lin.EMBL_RF00028_Intron_gpI_1298201813_4_16, i.e. #17 of that WU. I'm still a bit away from the deadline (29th it is), but can you tell me the crunch time 'til now? I want to update my BOINC, but can't until that monster is doneTrotador hat geschrieben:Hi,
This one is reaching its deadline but it's still running (at 100%):
cms_GA[e30-50MB_Lin64f]_Oryza-sativa-Indica-Group_CM000129.lin.EMBL_RF00028_Intron_gpI_1298201813_4_3
, I'm now at 417h, if I compare our benchmarks, I will crunch for another ~150-200h, that's less than 10 days, yeah! 
