Solved

---

http://allprojectstats.com/ts593244b0a.png

Thanks Joe, learned something new.
The crunching laptops I know had their power scheme adjusted straight away.

To change the thread title:
Make new post (not reply/quote).
Edit that post - you can then edit the thread title as well.
NB only possible if it's your thread

To have a thread closed (locked by moderator):
Request locking by using red-x (below post) on your post.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Kudos to Joe, Joe you nailed it 1st time out. When I got home I found that the green energy function was turned on. I went in and changed the turn off video part and reset everything related to what boinc needs. It worked, a new task has started and it is looking like a normal amount of time elapsed.

Thank you all very much for your input and a special thanks to you Joe.

On a separate note how do you tag this thread as resolved?

---

http://allprojectstats.com/ts593244b0a.png

Additional thought - a zero crossing error? Has there been a change in the way sweep angles are calculated when the start and finish angles are the opposite sides of zero?

(Start = 10; end = 350 might give the erroneous result of 340, or the correct result of 20 depending on how the calculation were performed)

No, it's a side effect caused by the multibeam recorder pausing when the ALFA receiver isn't in use. For that 26jn12ab.13707.20530.13.10.189 WU, it actually paused 3 times so there are 4 short sections of unrelated data:

13.0 seconds from June 27 04:17:23.1 to June 27 04:17:36.1
6.95778 hour gap
38.0 seconds from June 27 11:15:04.3 to June 27 11:15:04.3
7.43139 hour gap
41.5 seconds from June 27 18:41:35.2 to June 27 18:42:16.7
16.8225 hour gap
14.7 seconds from June 28 11:31:37.9 to June 28 11:31:52.6

That's an extreme case, but doesn't directly relate to tasks taking too long. The extremely high AR is not right but simply means the science application does relatively few calculations.


With Run time 75,503.05 seconds and CPU time 2,193.03 seconds on that 6.03 CPU task 2935358446, IMO BOINC thought it was running when it actually wasn't getting much CPU time. The two valid tasks from the same group also show a large discrepancy between run time and CPU time.

On the GPU Astropulse tasks, my guess is the laptop may be set to turn off video after some period of no keyboard or mouse activity. With the emphasis on being "green", that means the GPU portion of the APU gets powered down and the GPU application cannot actually do anything useful. But the application has CPU code too which is waiting for the GPU to finish something so it can be told what to do next.

That could be using a lot of CPU cycles when the GPU is powered down, and is running at higher priority than the 6.03 CPU application. So possibly that explains why 6.03 is also running slowly.

                                                                  Joe

The AR isn't the issue - two tasks of that batch have validated and on the errored ones the wingmates crunched successfully.

The error on 3 of the 4 tasks is 'time limit exceeded' and even on the valid tasks wall time is far above cpu time.
IOW boinc isn't getting enough cycles - AFAIK it runs a lower priority so any normal processes will snatch CPU time from boinc. boinc sits there patiently waiting for free CPU but keeps counting the time - that is needed to adjust runtimes to normal systemload values. In your case boinc is spending far too much time waiting and then decides it has taken too long.

Check how much CPU% the boinc process is getting (task manager) - with two cores you should see 50% on one thread and almost 50% on the other. If it's significatny less than that you have a problem.

Something is nagging me about those being APUs...

You could try reducing crunching to one core or to set 'Suspend work when non-BOINC CPU usage is above x%' to a higher value - iirc the default is a ridiculous 25% - you could try a setting of say 80?

HTH

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

I saw the angle info but I am not sure that this is the issue. The laptop is taking a huge amount of time to do tasks.

I have never used windows 8 before and it looks like there are a huge amount of tasks happening. There is what looks like a bunch of apps running, could this be what is going on? (my pc exp stops at windows xp)

---

http://allprojectstats.com/ts593244b0a.png

Additional thought - a zero crossing error? Has there been a change in the way sweep angles are calculated when the start and finish angles are the opposite sides of zero?

(Start = 10; end = 350 might give the erroneous result of 340, or the correct result of 20 depending on how the calculation were performed)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Is that really 347deg - I think there's some thing wrong with that unless they were using a military search radar...

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

On the cpu tasks that have errored the true angle range is a lot bigger than I have seen before, I thought the max was below 20.

WU true angle range is : 347.224800

This may be a clue, to someone with more knowledge.

Sorry not a computer wiz, I just got a new laptop and added it to my team and the tasks are taking 30+ hours or are coming with errors. Would someone take a look at the few tasks I have completed.

Here is my Boinc start:


2013-04-23 10:53:57 PM | | No config file found - using defaults
2013-04-23 10:53:57 PM | | Starting BOINC client version 7.0.28 for windows_x86_64
2013-04-23 10:53:57 PM | | log flags: file_xfer, sched_ops, task
2013-04-23 10:53:57 PM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
2013-04-23 10:53:57 PM | | Data directory: C:\ProgramData\BOINC
2013-04-23 10:53:57 PM | | Running under account Robert
2013-04-23 10:53:57 PM | | Processor: 2 AuthenticAMD AMD A6-4400M APU with Radeon(tm) HD Graphics [Family 21 Model 16 Stepping 1]
2013-04-23 10:53:57 PM | | Processor: 1.00 MB cache
2013-04-23 10:53:57 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm svm sse4a osvw ibs xop skinit wdt lwp fma4 page1gb rdtscp
2013-04-23 10:53:57 PM | | OS: Microsoft Windows 8: x64 Edition, (06.02.9200.00)
2013-04-23 10:53:57 PM | | Memory: 7.46 GB physical, 8.59 GB virtual
2013-04-23 10:53:57 PM | | Disk: 673.04 GB total, 627.18 GB free
2013-04-23 10:53:57 PM | | Local time is UTC -7 hours
2013-04-23 10:53:57 PM | | ATI GPU 0: Scrapper (CAL version 1.4.1741, 512MB, 480MB available, 658 GFLOPS peak)
2013-04-23 10:53:57 PM | | OpenCL: ATI GPU 0: Scrapper (driver version CAL 1.4.1741 (VM), device version OpenCL 1.2 AMD-APP (938.2), 512MB, 480MB available)
2013-04-23 10:53:57 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 6972907; resource share 125
2013-04-23 10:53:57 PM | SETI@home | General prefs: from SETI@home (last modified 12-May-2011 22:26:07)
2013-04-23 10:53:57 PM | SETI@home | Computer location: home
2013-04-23 10:53:57 PM | | General prefs: using separate prefs for home
2013-04-23 10:53:57 PM | | Reading preferences override file
2013-04-23 10:53:57 PM | | Preferences:
2013-04-23 10:53:57 PM | | max memory usage when active: 3821.13MB
2013-04-23 10:53:57 PM | | max memory usage when idle: 6878.03MB
2013-04-23 10:53:57 PM | | max disk usage: 10.00GB

The APU/GPU is ATI 7520

Thanks in advance
Robert

---

http://allprojectstats.com/ts593244b0a.png