http://srbase.my-firewall.org/sr5/result.php?resultid=359194127

More than 11 days of calculation and "task declared too late" = 0 credit

WTF !!!

I had other 3 running with same duration, I just canceled them.

What a poorly developed application.

Yes I have an iMac (late 2009), HT is not an option here (you can't switch it off).

It is a problem ?

I think I remember this is not the first time I have that issue (never ending long 2 task), I have removed that app in my preferences.


(btw I forgot to say "hello" but i was a bit upset, sorry for that)

just use mt, it helps to get them back within the deadline

I don't understand "just use mt" ?

use app_config.xml to say boinc, that llr should use multiple cores for one task

It is in the FAQ thread here http://srbase.my-firewall.org/sr5/forum_thread.php?id=6

Interesting, I didn't know about the multi-threading on SRBase, I knew about it on Primegrid and have implemented it there.

I have an SRBase Long2 running now for over 10 Days, 4 days past deadline, saying it is at 98.692% and 3.15 hours to go.
Those 3.15 hours will take 1 to 2 days at least to run (they are not very accurate estimates).

The computer is in HT mode (an Intel Xeon) and I wont be changing that.

I will however use that link and get my app_config.xml file created and installed on each computer running this project, in the next few days.

That link is dated to last year, how observant am I?

Thanks for the link and the information.

Conan

Regarding the mt : now I remember that, I even think I had implemented it long time ago. But obviously it got lost in my boinc setup somehow...

I will look at that solution again, thanks.


@Conan: I'm afraid that this task running on your machine is lost, when mine terminated (normally) it had been running at 99,99% for some time already but it was several days overdue, and the assimilator or validator (or whatever it is called) had no mercy...

Strangely the other 3 were still running at 99,99% when I decided to kill them - it made no difference for credit, maybe it did a difference for "science" and it was silly to do that by that time after waiting so long, but I was upset.

I did the app_config thing, I'll see what happens the next time I get some SRBase in my machine.

Thanks.

Yes, well, after doing the app_config.xml, I now get nothing but errors.

I will check to see if it is in the wording >-t4< or as I have it >-t 4<, like I have at Primegrid.

Conan

Mine work using <cmdline>-t4</cmdline>

Wuprop only counts 1 thread though.

Thanks PDW,

Adjusted that line, so we will see what happens.

Conan

I got lucky with that long running task of mine, it ran for over 972,000 seconds (270 hours or 11.25 Days), and I managed to get it back first, so got the points.

That is what single thread does, here's to MultiThreading doing it a lot quicker.

Have to wait now for BOINC to grab new tasks, could be a few days on that machine, it will have to let other work run first.

Conan

Thanks PDW,

Adjusted that line, so we will see what happens.

Conan

I have downloaded and am now running a Long2 work unit. After 8 hours it shows over 14% done, which is a lot quicker than before.

@ PDW,
I am showing all 4 threads on a 4 core computer being recorded at WUProp, 8 hours done and showing 31.6 hours, which seem right to me.

I do have an extra line in my app_config.xml file that may be what is different to what you have.
I have
<cmdline>-t4</cmdline>
<avg_ncpus>4</avg_ncpus>

Not sure if this might be how I am getting all threads picked up or not.

Anyway all seems to be working again,

Thanks
Conan

You have all your app_versions as "srbase" and not "srbase2" "srbase12" etc...

Just cancelled bunch of "long" wu's (I gave it a chance; some wu's were running for 4+ days and at 95%). Short wu's fine, but i'm not going to waste anymore resources to this "long" sh*t!

See ya!

Here is what I've wound up using on my 4790K, and it seems to work quite well - I DID have to add the "ncpus" in there so BOINC would report them as using 3 CPUs. I also note that usage never gets over about 130% (100% = 1 core) even though 3 are specified. Other apps run up to 287%. However, it works, I'm not going to mess with it.

I've only included srbase12 here - obviously you can replicate this for the other 11...

<app_config>

<app>
<name>srbase12</name>
<max_concurrent>1</max_concurrent>
<fraction_done_exact/>
</app>
<app_version>
<app_name>srbase12</app_name>
<cmdline>-t3</cmdline>
<avg_ncpus>3</avg_ncpus>
</app_version>

<project_max_concurrent>1</project_max_concurrent>
<report_results_immediately/>
</app_config>

I had to abort several "long3" wus as there was no way they were even going to START before the deadline. These deadlines seem very short for such long tasks - I am set for one days work plus one day extra, yet got like 10 long3's, each around 11 hours runtime, that were due three or four days later. Even if no other projects were running I couldn't have made it. It's possible that the overload was due to messing around with app_config, so I'm not sweating that yet.