|
1)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1640)
Posted 8 Apr 2016 by Traills Post: thnx |
|
2)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1638)
Posted 8 Apr 2016 by Traills Post: Eric, One of those two long Qsqrt421_DS3x8 WUs we emailed about last weekend has finished (15161027, after ~358,000 cpu sec on my i7) but the other one may need your help for a 1- or 2-day extension, please. It is 15161313 (wu_Qsqrt421_DS3x8_CV1_S815_N2_-194151_N1_806084_0), due 5 a.m. Saturday UTC. It has over 7 days running now which I hope not to lose. It has been stuck showing 5/7ths done (71.428%) for a couple of days so it's probably about ready to roll another 1/7, It still might finish on time Friday night, but I will not be able to monitor it (will be traveling). If you can keep it alive 'til it's done, I'll appreciate it. Thanks/ Traills |
|
3)
Message boards :
Number crunching :
Super long estimated times
(Message 1232)
Posted 26 Feb 2015 by Traills Post: Something similar going on in several of my Get Decics with Bounded Discriminant v3.00 WU's. The last one was showing 10:36:09 worked - not bad in itself, but only 26.233% complete, and that represented just an 0.1% increment in completion over its last 26 CPU minutes (i7-3770 @3.4GHz). ETC inflated by 63 minutes in the same time period. I normally wouldn't mind letting a WU crank for as long as it takes (I also participate in CPDN). This one I thought it best to abort because to keep it around was projecting a risk to other WUs that were waiting in the queue. Cumulative result of two other v3.00 WUs running to completion in the 25-30 CPU hr range in the last week - although some are much shorter - coupled with a lot of Decic Fields 1.02 WUs running 10-25 hrs lately. Not sure what can be done; maybe increase the due date for all WUs by some further percent until the tasks return to a more moderate part of the problem space. |
|
4)
Message boards :
Number crunching :
PRogress meter not updating
(Message 5)
Posted 14 Aug 2011 by Traills Post: More beta info, 1. stderr continues to report memory leaks on all completed tasks regardless of runtime, but there is no evidence of leak build-up on the computer. Most completed tasks finished in only a few minutes, which seems wrong (not consistent with what I see on the WU lists for your computers), and a minority take several hours, which seems right. 2. Aborted task 8174 after around 10 hrs run time, BOINC manager displaying "---" for the "Remaining" time on that task where it had been stuck for awhile. Lack of progress meter working makes interpretation of where the process is at dicey. Don't know if solution truly hung or endless-looping, or maybe the estimation algorithm for remaining time had a problem. This is the only task I have seen that behavior on so far. |
|
5)
Message boards :
Number crunching :
PRogress meter not updating
(Message 4)
Posted 14 Aug 2011 by Traills Post: Hi Eric - Just a couple of kinks noticed in your beta. (1) Progress meter is not updating in my Boinc Manager window, on either system (one running XP SP 2, the other running Windows 7 SP 1). (2) 4 tasks have finished early, 300 - 830 cpu sec - while 4 others are continuing in progress well beyond that as I expect they should. All 4 early tasks list as validated (min quorum=1 though) but also reported memory leaks to stderr. If the leaks were real, they seem not to have persisted. My system monitor shows no indication of orphaned memory or of memory growth tagged to any process. |