should i let it run or abort?
at 97,434% and 15:27:27 !!!!

Name 2XP_16101430_3600_4300_1


Workunit 13820670
Created 16 Oct 2015, 12:34:40 UTC
Sent 16 Oct 2015, 14:13:24 UTC
Report deadline 27 Oct 2015, 3:33:24 UTC


Application version Carro-Rodriguez-Laguna-Pueyo Epicardial Model (Carro et al. 2011) for human ventricular cells v1.05

Hi,

This task is one of the largest task we have seen in our project. It will cost more than other tasks we have launch. Also the checkpoint seems to made it even slow than other WUs. Also the last part of the simulation is the critical part of storing the information in the file. This part have to been made without checkpoints, so it could be the reason that your task is stuck at this percentage.

I will let it one day, if it doesn't change it, abort it.

Best regards, Joel.

OK.

Hi, all! I have five WUs stuck at 100%. Their elapsed times are as follows:

40:18:04
18:49:58
09:51:52
09:50:38
09:36:39

All of them on the same PC. They were running until I suspended the project. That same PC has other Denis' WUs waiting to be crunched.

Should I let them crunch or abort these five? And how about the others?

Many thanks,
Valter.

had abort the WU above mentioned...

well, ich got 4 or 5 tasks, estimated duration 3 or 4 hours, the two first tasks seem to last about 13-15 hours. the other tasks i aborted before beginning..
the first one is uploaded now, 100%! and, since i got a day of time only, it was uploaded to late..
seems to be a little bit frustrating for me....
is this happening now with every single task?
well, i crunch because i crunch...but...

well, ich got 4 or 5 tasks, estimated duration 3 or 4 hours, the two first tasks seem to last about 13-15 hours. the other tasks i aborted before beginning..
the first one is uploaded now, 100%! and, since i got a day of time only, it was uploaded to late..
seems to be a little bit frustrating for me....
is this happening now with every single task?
well, i crunch because i crunch...but...

Hi!
The issue of 100% occurs randomly and we didn't know exactly what is related to. We are testing with different delay bound to test how fits bet this size of task.

Best regards, Joel

thx a lot joel, that calms me down...
my second task was estimated around 3 hours and is now at approx. 18 hours, 98,5 percent..
i know, the credit i get for that is zero..
but lets see, what your magic is doing on this calculation-bug ^^

thx a lot joel, that calms me down...
my second task was estimated around 3 hours and is now at approx. 18 hours, 98,5 percent..
i know, the credit i get for that is zero..
but lets see, what your magic is doing on this calculation-bug ^^

wol,
It looks like the common element on the systems with the long run time is they are running 32-bit Linux. You might just run a short test on your setup to see if will complete a DENIS computation. The DENIS source build tree has a 13-line text input test case that should run in less than a minute. It might help isolate the problem.

You can go to the boinc project directory ( probably something like /var/lib/boinc/projects/denis.usj.es_denisathome/ ) and create a file name "in" with the contents of the test case (below). You will see the other configuration input files in that directory named <task>.conf and can look at their contents.

You should find the Denis application executable binary there. It will have a name something like "CRLP2011EPT_105_i686-pc-linux-gnu"

You should be able to execute that application with no parameters and it will look for the "in" file by default and it should create an output file "out" by default.

time ./CRLP2011EPT_105_i686-pc-linux-gnu

TEST CASE lines for "in":
3000
0.002
50
2900
5
26 0.002
36 0.00
41 12.29
47 0.0673
56 25.0
2
0
1

the test case is from:
https://github.com/DENISproject/denis-boinc-baseapp/blob/master/in

hey rjs5,


ok first: you are right, im using 32 bit linux. i have done that test case and it was solved in about 30 seconds.
(my second denis task is about 29 hours now, 99.98 percent)

results (i think you are more interested in the time):
# time /var/lib/boinc-client/projects/denis.usj.es_denisathome/CRLP2011EPI_105_i686-pc-linux-gnu

real 0m31.036s
user 0m28.904s
sys 0m0.048s

hey rjs5,


ok first: you are right, im using 32 bit linux. i have done that test case and it was solved in about 30 seconds.
(my second denis task is about 29 hours now, 99.98 percent)

results (i think you are more interested in the time):
# time /var/lib/boinc-client/projects/denis.usj.es_denisathome/CRLP2011EPI_105_i686-pc-linux-gnu

real 0m31.036s
user 0m28.904s
sys 0m0.048s

Finishing the "in" file is good. That means that DENIS should be OK. DENIS is just taking a long time running the standard APP at the 500MHz or so that your AMD A8-7100 is clocked at. Denis only requires several MB of memory so it will not strain your capacity. If you run several different apps, I would periodically check for swapping. Swapping could kill you.

The standard DENIS app was taking 10 seconds and the optimized app was taking about 1.5 seconds on a VM that I was testing. I would probably let the 29-hour app finish but would install one of the optimized 32-bit apps which should execute 5 to 10 times faster.

You should be able to successfully run the crunchr optimized SSE3 32-bit linux app and it should run many times faster than the standard DENIS app.


Linux 32bit SSE3(INTEL/AMD compatible):
http://www.boincunited.org/opt_apps/denis/denis_1.05_x86_32-pc-linux-gnu__sse3_v3.tar.bz2

Linux 32bit SSE2(INTEL/AMD compatible):
http://www.boincunited.org/opt_apps/denis/denis_1.05_x86_32-pc-linux-gnu__sse2_v3.tar.bz2


From BritishBob .... install instructions ...
My standard check list when swapping the optimized apps:
-Disable new tasks (in client)
-Let the current tasks finish.
-Close BOINC Client.
-Exit BOINC client in bottom right icon menu thing (name escapes me atm)
-Copy APP to the proper location detailed somewhere above (I have it on a shortcut)
-Open up BOINC
-Allow new tasks

hey rs,

thats a totally new level of crunching for me...
specialized apps...
didnt even know that such things exist!

anaways,thank you for your help and tutorials!
i upgraded to linux 64 bit now and will look into this :-)