Recently it appears there were some changes made at SETI on the server side that resulted in my version of boinc, 6.2.14, not receiving any AP work. At least that is what I think was going on. I made a couple of posts in “Panic Mode On (89) Server Problems?” about what was going on and also asked if anyone else was still having problems with 6.2.14 after the server side code was adjusted but did not receive any response.

As a result I changed my version of boinc to 7.2.42 and that seemed to cure the problem of not obtaining any AP work. Now however I am seeing a lot of AP WUs taking 83-84,000 seconds to complete when the most I ever saw in the past was 40,000 seconds and generally most WUs fell in the 34-35,000 second range.

Is there something I do not know about boinc 7.2.42 that is resulting in increased processing times or am I just seeing a weird set of AP units?

I have not seen anything posted about increased processing times for AP WUs and the credits I am receiving for the 80,000+ second times are still about the same on average as I was receiving for the 35,000 second times so something does not seem quite right somewhere along the line.

This on a Linux server using ap_6.01r546_sse3_linux32. Thanks.

This on a Linux server using ap_6.01r546_sse3_linux32

Your Stderr shows stock app, not SSE3
http://setiathome.berkeley.edu/result.php?resultid=3722293458

Only one task with Run time 0 is by SSE3
http://setiathome.berkeley.edu/result.php?resultid=3678819857

Edit:
The above SSE3 Stderr is from the time you used BOINC 6.2.14
There are some other SSE3 done tasks all under BOINC 6.2.14
Obviously you deleted app_info.xml manually (since the new BOINC installation will not do that by design, it have to preserve the BOINC Data directory)
 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Disregard. I think I figured it out. When I installed boinc 7.2.42 I also received in the bargain "AstroPulse v6 v6.01" which boinc decided to use instead of ap_6.01r546_sse3_linux32. I redid app_info.xml to reflect the correct app and hopefully that will fix the problem. Sorry for the false alarm. It has been years since I installed 6.2.14 and I had forgotten what was involved.

This on a Linux server using ap_6.01r546_sse3_linux32

Your Stderr shows stock app, not SSE3
http://setiathome.berkeley.edu/result.php?resultid=3722293458

Only one task with Run time 0 is by SSE3
http://setiathome.berkeley.edu/result.php?resultid=3678819857

We must have been typing at the same time. Thanks for the suggestion. I believe you are right. It seems logical. Thanks again.