[Karl Schimanek]

Originally Posted by Karl Schimanek 

Alex, what's about DTrace? Maybe a better option than Shark?

Regards

DTrace

[adream]

this is how my 8-core rac graph looks like,

appears that it has reached the limit of RAC

pretty bleeding amazing tho :-)

regards

adream

[zombie67]

Yep, mine looked almost exactly the same. Mine topped out a few hundred less. I could probably make up the difference if I didn't use it as my daily work machine. I am now adding other projects, so you will see the RAC drop dramatically.

[bobpalmer]

I had renamed the app_info.xml file when boinc was not recognizing anonymous platform. Yesterday boinc started running WU's with a new app version 518. I don't see anything in the log file going back to May 29 about downloading a new app version. Of course the new version 518 is not optimized, and the run times are ridiculously long.

2007-06-20 02:37:48 [SETI@home] Starting task 21fe99aa.15509.22386.61078.3.207_0 using setiathome_enhanced version 513
2007-06-20 02:50:58 [SETI@home] Starting task 12ap99aa.21719.22673.179842.3.107_0 using setiathome_enhanced version 518

Is Alex's optimized code compatible with version 518 requirements? I had been running seti_enhanced-ppc-v7.1-g5-nographics.

-- B

[adream]

same thing happened to me

boinc dumped the optimised client and ran unoptimised for a day, hence the sudden drop in RAC

i just reinstalled the optimised app and all is well

mine was also running without an app info file quite happily for a couple of weeks, i think they changed something on the server and its all back to normal now

regards

adream

[arkayn]

Right now I only have the 513 settings in my app info file due to the problems with the 5.9.X line of workers. I will add in anything else when they come out with the new workers.

[beadman]

Alex: Help!!

I was running the seti_enhanced-i386-v7.2-coreduo-nographics, with the correct app_info.xml version on my MBP and some time last night, BOINC downloaded the default.setiathome_5.18_i686-apple-darwin version which increased my times by about 25%. I took it back out and restarted the enhanced version. Are we going to have to check daily to make sure we're running the correct client?

beadman

[zombie67]

Sounds like the app_info.xml needs to be updated to account for this. I don't know how though.

[Odysseus]

Originally Posted by zombie67 

Sounds like the app_info.xml needs to be updated to account for this. I don't know how though.

It should just be a matter of changing the version entry, or adding another one, like this:
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>518</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v7.1-g4-nographics</file_name>
<main_program/>
</file_ref>
</app_version>
(Of course the file_name should be that of whichever optimized app you’re running.)

@Alex (or anyone who’s “in the loop”): any idea of when optimized apps based on the v5.18 (or later) sources might become available?

[arkayn]

Looks like I might have to put back in Alex's original app_info file now. It has all the stops up to 5.18.

[beadman]

Alex:
Don't know if you've seen this before or not, but I'm getting some errors in my work units - doesn't affect validation, but thought I'd mention it anyway. The stderr out says:

<core_client_version>5.8.17</core_client_version>
<![CDATA[
<stderr_txt>
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
OS X optimized S@H Enhanced application by Alex Kan
Version info: OS X SSE3 (Intel, Core Duo-optimized v7.2-nographics) V5.13 by Alex Kan

Work Unit Info:
...............
WU true angle range is : 0.433785
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
OS X optimized S@H Enhanced application by Alex Kan
Version info: OS X SSE3 (Intel, Core Duo-optimized v7.2-nographics) V5.13 by Alex Kan

Work Unit Info:
...............
WU true angle range is : 0.433785

Flopcounter: 16036158013403.041016

Spike count: 0
Pulse count: 1
Triplet count: 3
Gaussian count: 0
</stderr_txt>
]]>
Validate state Valid

Hope this helps...
beadman

[Odysseus]

Originally Posted by beadman 

MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107

This has come up here before, somewhere upthread, and also in the S@h Mac Q&A forum (where IIRC Alex indicated that he’s aware of it). It’s apparently triggered by an attempt to give the executable file its green-dish icon, which fails due to some kind of permissions issue; it happens with the stock v5.13 apps as well.

[beadman]

Originally Posted by Odysseus 

This has come up here before, somewhere upthread, and also in the S@h Mac Q&A forum (where IIRC Alex indicated that he’s aware of it). It’s apparently triggered by an attempt to give the executable file its green-dish icon, which fails due to some kind of permissions issue; it happens with the stock v5.13 apps as well.

Ok, thanks for the info. I hadn't seen that. Just thought I mention it just in case.

beadman

[bobpalmer]

Originally Posted by Odysseus 

It should just be a matter of changing the version entry, or adding another one, like this:
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>518</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v7.1-g4-nographics</file_name>
<main_program/>
</file_ref>
</app_version>

I would assume that there are different results expected from different versions. Just changing the version_num in the app_info.xml would not change the fact that Alex's V7.1 was written as a version 513 app. But then maybe someone has better information about what the changes are between 513 and 518. In the past, S@H stopped sending WU's if the app was too old.

[kennet]

559019275 136959645 26 Jun 2007 8:57:40 UTC 26 Jun 2007 16:09:26 UTC Over Client error Aborted 0.00 0.00 ---
559019255 136959613 26 Jun 2007 8:57:40 UTC 26 Jun 2007 13:13:04 UTC Over Client error Aborted 0.00 0.00 ---
559019131 136959579 26 Jun 2007 8:57:40 UTC 26 Jun 2007 14:35:52 UTC Over Client error Aborted 0.00 0.00 ---
559018769 136959464 26 Jun 2007 8:57:40 UTC 26 Jun 2007 19:28:00 UTC Over Client error Aborted 0.00 0.00 ---
558863667 136909323 26 Jun 2007 5:07:55 UTC 26 Jun 2007 11:50:21 UTC Over Client error Aborted 0.00 0.00 ---

Ever since I have been using 5.10.7 there have been over an hundred occurrences of this error. The one saving grace is that there is no time consumed on the work units. Of course there is the time downloading and the invalidated effort by both the user and Boinc.

Contrary to others here my application never did download 518 and still is using 513.

Has anyone else experienced this error?

Is it Boinc side or our side?

Kenn

[adream]

Originally Posted by kennet 

559019275 136959645 26 Jun 2007 8:57:40 UTC 26 Jun 2007 16:09:26 UTC Over Client error Aborted 0.00 0.00 ---
559019255 136959613 26 Jun 2007 8:57:40 UTC 26 Jun 2007 13:13:04 UTC Over Client error Aborted 0.00 0.00 ---
559019131 136959579 26 Jun 2007 8:57:40 UTC 26 Jun 2007 14:35:52 UTC Over Client error Aborted 0.00 0.00 ---
559018769 136959464 26 Jun 2007 8:57:40 UTC 26 Jun 2007 19:28:00 UTC Over Client error Aborted 0.00 0.00 ---
558863667 136909323 26 Jun 2007 5:07:55 UTC 26 Jun 2007 11:50:21 UTC Over Client error Aborted 0.00 0.00 ---

Ever since I have been using 5.10.7 there have been over an hundred occurrences of this error. The one saving grace is that there is no time consumed on the work units. Of course there is the time downloading and the invalidated effort by both the user and Boinc.

Contrary to others here my application never did download 518 and still is using 513.

Has anyone else experienced this error?

Is it Boinc side or our side?

Kenn

AFAIK thats not an error Kenn, thats a new feature !

once theres a quorum of two reached with results database then your boinc manager is told that crunching these WU's is unnecessary so your manager aborts em

save you crunching stuff that has already been returned and checked against another result

theres lots of talk whether this effects RAC etc but to me it seems like a good idea as far as the science and our electricity bills are concerned crunching only what is needed

regards

adream

[BTBlomberg]

So adream, this is likely more of a problem if one has <work_buf_min_days> set too high in their global_pref file? I say that because if the machine is not fast enough to cruch a WU in time to reach participation in the quorum one must be fetching too many days of WUs. If so one would get stuck in a pattern of "Errors" like kennet.

If so kennet may need to back this value off. Right?

[adream]

yup instinctively i would say that big caches on slow computers will be effected unless it updates often which doesn't seem to happen

im trying to drop my cache down to a day or so but have 800 ghost wu's on my 8-core :-)

regards

adream

[kennet]

Originally Posted by kennet 

559019275 136959645 26 Jun 2007 8:57:40 UTC 26 Jun 2007 16:09:26 UTC Over Client error Aborted 0.00 0.00 ---
559019255 136959613 26 Jun 2007 8:57:40 UTC 26 Jun 2007 13:13:04 UTC Over Client error Aborted 0.00 0.00 ---
559019131 136959579 26 Jun 2007 8:57:40 UTC 26 Jun 2007 14:35:52 UTC Over Client error Aborted 0.00 0.00 ---
559018769 136959464 26 Jun 2007 8:57:40 UTC 26 Jun 2007 19:28:00 UTC Over Client error Aborted 0.00 0.00 ---
558863667 136909323 26 Jun 2007 5:07:55 UTC 26 Jun 2007 11:50:21 UTC Over Client error Aborted 0.00 0.00 ---
Kenn

If you check the times here you will see that the WUs did not sit more than an half day. In many cases they sat for as little as two to three hours on my computer.

This computer has a RAC of 2300. I have reduced, as indicated in a previous email, the
number of days cache to one.

Kenn