Well Beyond, it has passed 252 Hours and is still running and still at 73.00%.
Care for another guess?

Conan

Conan, looks like you're running this WU: WU=17810575
Judging from the speed of the one machine that completed it vs. your machine I'd say you're looking at around 10-11 days total for this WU. It should complete though if your computer doesn't do something untoward (such as reboot).

Beyond, yes that is the one.
It has passed 200 hours now still at 73% and last checkpoint was at 24 hours.
But still running and using a full core so we will see how it goes, must finish soon?

Well I guess then that my 141 hours and stuck at 73% for over 2 days, has a way to go.
Still taking up a full core so letting it run. Would be nice to get many, many thousands of credit for it (ha, ha).

Conan

There are about 30 TCGA workunits still around and for sure those are the very long ones. Theoretically those could run forever. The reason is that for a certain, very rare, type of input the algorithm's completely is exponential. We usually manage to adjust the input dataset in order to avoid this but in the current case there were an issue that we were able to fix only after the workunits were distributed. The results are of scientific value, of course, but without a checkpoint inside the critical section of the algorithm this is not the kind of computation to do inside the BOINC framework.

Anyway, I will wait for them for another couple of days then I will abort them server side, I will figure out a way to give credits even in this case.

Interesting. I have followed link on task info page to get info about CPU and OS, so looks that sometimes crashes occur on 2700 too. Unfortunately today this task page is deleted so I cannot add link here. Anyway, I will update my report that bug happens mostly on 1700.

There are about 30 TCGA workunits still around and for sure those are the very long ones. Theoretically those could run forever. The reason is that for a certain, very rare, type of input the algorithm's completely is exponential. We usually manage to adjust the input dataset in order to avoid this but in the current case there were an issue that we were able to fix only after the workunits were distributed. The results are of scientific value, of course, but without a checkpoint inside the critical section of the algorithm this is not the kind of computation to do inside the BOINC framework.

Anyway, I will wait for them for another couple of days then I will abort them server side, I will figure out a way to give credits even in this case.

Here's the longest one I've seen yet:

http://gene.disi.unitn.it/test/workunit.php?wuid=17810256

I suspect the 4 "Timed out - no response" instances are still crunching away. My example is on a pretty slow machine. It's at 137 hours and 12%. It looks like these aren't checkpointing often. This WU is showing 117 hours since the last checkpoint (in BoincTasks).

Now at 183 hours, and 156 hours since the last checkpoint (which is troubling). Still at 12%. I assume that if the computer reboots or the WU gets interrupted for any reason it will restart. It appears that 6 computers are currently running this WU and no one has finished it. Is it viable?

Is fma faster than avx on the Ryzen 1700?

It seems to be just slightly, though they are so close that it would take longer-term testing to be sure. I think it would be easier for the project to find the best extension for a given processor type, and just use it.

Thanks a lot. I substituted "fma" for "avx", and it is running fine on my Ryzen 1700, making it productive again.

Here's the longest one I've seen yet:

http://gene.disi.unitn.it/test/workunit.php?wuid=17810256

I suspect the 4 "Timed out - no response" instances are still crunching away. My example is on a pretty slow machine. It's at 137 hours and 12%. It looks like these aren't checkpointing often. This WU is showing 117 hours since the last checkpoint (in BoincTasks).