21)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1622)
Posted 27 Mar 2016 by Dj Ninja Post: Okay thank you. But let me finish the other one! |
22)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1619)
Posted 27 Mar 2016 by Dj Ninja Post: In this case I want to abort #16197688. Or do you want to double-check it? Just doing such a WU for fun doesn't seem efficient to me. |
23)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1617)
Posted 26 Mar 2016 by Dj Ninja Post: The tasks you listed as "heavy" on my i7 machine have both started. While #16197688 looks not this much disturbing for now (47.463% after 92:12:00), #16374076 could provide some fun. It's hanging around at 0.038% after 22:36:00, resulting in an estimated finishing time in a couple of years. Well, let's see. My plan is to let them run, hoping the max_time and max_ops values are set high enough to not get the WUs killed by the Boinc Manager. Fortunately the machine is stable and really fast at NumberFiels and both tasks are on the same machine. I should be able to complete these WUs. |
24)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1616)
Posted 26 Mar 2016 by Dj Ninja Post: Some projects are black holes that consume all the CPU you give them with no sense of progress. That's true for most of the projects. Aside a good progress indicator (which virtually stands still at large WU batches) I like to know if I found something important. That's why I'm inspecting WU output files from extraordinary WUs or when I reconize an unusual file size. On Primegrid you have a list of all primes you found. I don't know how many fields or "important polys" are found during the process or within a normal day, but if they are very rare such a list (or a counter when not that rare) will be nice here too. Don't care that much about cheaters. If they need more credits than others for compensating their bad live, they won't stop even if there is an upper limit. This limit gets worked out then maxed out without beeing reconized by the script. My approach to counter this would be calculating how much polys where tested over time and comparing this against processor capabilities. Even I won't grant credits based on benchmark/time relations, but for tested polys. This will give the same amount of credits for the same amount of work regardless of which processor has finished the WU or how good or bad the benchmark results have been. |
25)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1611)
Posted 25 Mar 2016 by Dj Ninja Post: The first two of my long running WUs I listed yesterday are down. Unfortunately, it found nothing. # Inspected 2731542253 polynomials. But I've reconized another problem regarding Boinc credits with these WUs. http://numberfields.asu.edu/NumberFields/result.php?resultid=16168378 ran for almost a week and scored 5,745.30 credits http://numberfields.asu.edu/NumberFields/result.php?resultid=16168357 ran for 4 days and 7 hours, scoring 5,745.30 credits too Shouldn't there be a difference between these two because of the 2 1/2 day longer running time? I assume that these WUs reach an upper limit in the credit calculation process. |
26)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1610)
Posted 25 Mar 2016 by Dj Ninja Post: Okay, that's good enough for me. One of the i7-3820's WUs I listed is now running for a week and that's a very fast machine on NumberFields. someone finishes the WU before you I don't think so... ;) |
27)
Message boards :
Number crunching :
Bug in PARI/GP (Segmentation Fault) - compute error
(Message 1607)
Posted 24 Mar 2016 by Dj Ninja Post: another one ... http://numberfields.asu.edu/NumberFields/workunit.php?wuid=14990272 |
28)
Message boards :
Number crunching :
Qsqrt421_DS3x8 15+ hour running time?
(Message 1606)
Posted 24 Mar 2016 by Dj Ninja Post: I don't know if this can be called "a handful". I've got an entire bunch of really long running ones, even on really fast machines like an i7-3820 at 4,4Ghz. These workunits will miss the deadline soon, you should think about extending the deadlines in general. I let these workunits run but I will be very disappointed when I can't get credit for it. http://numberfields.asu.edu/NumberFields/result.php?resultid=16168339 http://numberfields.asu.edu/NumberFields/result.php?resultid=16168357 http://numberfields.asu.edu/NumberFields/result.php?resultid=16168378 |
29)
Message boards :
Number crunching :
Bug in PARI/GP (Segmentation Fault) - compute error
(Message 1604)
Posted 17 Mar 2016 by Dj Ninja Post: Hi there! I had one of these WUs too which crashed with the PARI segmentation fault. http://numberfields.asu.edu/NumberFields/workunit.php?wuid=15008080 |