Hi,

I´m new to Moo and I wonder if my ATI can help in the processing of WU´s. I have updated to the latest version of driver, but I´m not sure if the GPU is used. How can I follow the process in an easy way? I´m using TThrottle and Boinctask from Efmer to supervise the processing. Much obliged to any help from your side.

Rgds
Bernt

---

You have been running successfully since you first joined. The times for WUs are horrendous though, as there are lots of pauses inserted into the processing of your WUs. The latter will be why you are getting lower results than you expected. Before we do the monitor bit, suggest the slow down needs fixing - we can talk re monitoring when thats done.

To see whats happening go to:

Account - Computers - task - look at Task Column - click on a blue number of a successful WU

You will see lots (dozens) of:

[May 30 08:31:26 UTC] Paused... (found flagfile)
[May 30 08:31:38 UTC] Running again after pause... (flagfile cleared)

I strongly suspect thats caused by a setting in BOINC Client at your end. Go to:

Tools - Computing Preferences - Processor Useage Tab - "While processor useage is less than",

.... and change what is probably set as 25% to 0%. You will not get pauses inserted into processing then. 0% means unrestricted use of CPU by BOINC. When its set to 25%, any use of CPU above 25% of its capacity shuts down BOINC - everything, until use goes below 25%. By setting it to 0% BOINC has unrestricted access, which is no issue as BOINC back's off when you want to do other tasks - it will still run however, and not shut down, just run slower. If the 0% setting causes too much screen lag - and it may do in some circumstances, tey a setting of 80% (which means only shut down if CPU use for non-BOINC tasks goes above 80%).

It could be also because of TThrottle - thats another discussion if its the case.

If you do that (or its TThrottle), then post again that alls well and you have increased processing times (or that its TThrottle), we can sort out methods for you to monitor wants happening in the normal scheme of life. I saw the slow down, assumed you would want that sorted first - apologies if no the case.

EDIT: Looks like its TThrottle, your Einstein WUs are being paused to death 24,000+ secs per WU. Looking like TThrotle is set too fiercely, and shutting down the CPU far too early in practice. Have a look at the temperature cut off for TThrottle, its probably set far too cautiously.

Regards
Zy

Thanks Zy for your comments. I will attend to this asap.

---

Zy,

If I set something called tjunction to default(100 celsius) the cpu% falls immed. to approx 10%. When I change it to 75C then the CPU % goes to 100% for Moo jobs but I got a warning from TThrottle " The core temperature is corrected ( Tjunction is not the default setting)" I´m not really sure how it impacts my processors, if it is dangerous or not. Maybe I shall put my question to Fred!

I will let work this way over night and see if I have a working PC tomorrow. I run 24/7.

Rgds

Assuming you have not overclocked the CPU, take out TThrottle so its not active. Moo!Wrapper is perfectly safe and has little impact on the CPU - certtainly not to the extent that TThrottle was built for.

You'll find at defaults the CPU temperature is perfetly OK. Once you are more used to overclocking - do that by slow steps not a big leap - the use of TThrottle will fall into place.

TJunction referes to a temperature limit set inside the TThrottle data files, and whether or not that particular limit set for your particular PC is applicable right now is debatable. Its clear that at present TThrottle is clobbering your PC to a crazy extent, and something is wrong with the configuration of TThrottle on your machine.

Take it out for now until you get into TThrottle a little more, with no overclock and normal useage you have no worries, and in any event the CPU will auto-dec lock itself if it gets too hot, which it wont unless the airflow inside your PC case is abysmal.

Download these two utilities, one monitors your CPU, the other your GPU. They are well used and respected, and do not write to your disk, so cant change squat - they are totally benign. Dont leave them running for extended poeriods (circa 10mins+) unless you really need to, as they can take away substantial resource when running.

http://www.alcpu.com/CoreTemp/ (choose 32 or 64 bit download as appropriate for your Windows version)

http://www.techpowerup.com/downloads/1978/TechPowerUp_GPU-Z_v0.5.3.html

If you have multi-gpu look closely for the drop down box and sensor tab to choose each GPU in turn.

You'll find by using these 99.9% of situations are covered by a regular quick check (say) once every 2 or 3 days. Its easy to construct an armagedeon scenario, but in reality useage at that frequency is fine for 99.9% of people. Certainly enough to keep you going until you get into monitoring needs and TThrottle useage (and its distinct limitations) a little more.

Do not hesitate to post if you have worries or concerns, the only dumb question is the one thats never asked ..... always someone on this board who will know the answer

Regards
Zy

What is the temperature of your CPU/GPU?
And how did you set Boinc preferences?
Always on?
Or suspend while active?

{edit}And BEFORE using GPU-Z, first pause Boinc to prevent freezes by the poor ATI drivers. When GPU-Z is up, you can resume Boinc.

You are superb Zy!

Thanks a lot for valid information!

Bernt

Always active! No rest just working!

Bernt

, but I´m not sure if the GPU is used. How can I follow the process in an easy way?
Rgds
Bernt

I now realize what the real question is!

You can see that in your Windows Task Manager (ctrl,alt&del choose 'processes')
In that list you see something starting with 'dnetc_1.02'.
If you are using the GPU, there is '_ati14.exe' in that line!
If not, I guess you using CPU only...

Can you copy the first 30 lines from your BM-message tab?

If you have a concern (been there done that:) ), just suspend Einstein for now, there is no chance in hell that the CPU will ever get too hot then - in fact I doubt it will even get warm rofl. Then just take it step by step. Suspending Einstein will give you a good night's sleep for now ..... but its actually unfair on Einstein because its safe enough as well, however first things first :) Once you get into monitoring needs a bit more, and the temperature lim its to watch for, turn it back on.

For now CPU and GPU to default, take out TThrottle suspend Einstein, attack the issue tomorrow. Just post when you are ready to go for temperature limits and what to watch for.

Regards
Zy

AAD,

I guess this is what you asked for.

Rgds

Bernt




2011-05-31 08:32:35 | | Starting BOINC client version 6.12.26 for windows_intelx86
2011-05-31 08:32:35 | | Config: GUI RPC allowed from:
2011-05-31 08:32:35 | | Config: 192.168.1.71
2011-05-31 08:32:35 | | log flags: file_xfer, sched_ops, task
2011-05-31 08:32:35 | | Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.5
2011-05-31 08:32:35 | | Running as a daemon
2011-05-31 08:32:35 | | Data directory: C:\Documents and Settings\All Users.WINDOWS\Application Data\BOINC
2011-05-31 08:32:35 | | Running under account boinc_master
2011-05-31 08:32:35 | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz [Family 6 Model 26 Stepping 5]
2011-05-31 08:32:35 | | Processor: 256.00 KB cache
2011-05-31 08:32:35 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 nx lm vmx tm2 popcnt pbe
2011-05-31 08:32:35 | | OS: Microsoft Windows XP: Professional x86 Edition, Service Pack 3, (05.01.2600.00)
2011-05-31 08:32:35 | | Memory: 3.00 GB physical, 4.84 GB virtual
2011-05-31 08:32:35 | | Disk: 931.51 GB total, 798.87 GB free
2011-05-31 08:32:35 | | Local time is UTC +2 hours
2011-05-31 08:32:35 | | ATI GPU 0: ATI Radeon HD 4350/4550 (R710) (CAL version 1.4.1385, 1024MB, 96 GFLOPS peak)
2011-05-31 08:32:35 | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 3942036; resource share 100
2011-05-31 08:32:35 | Milkyway@home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 262775; resource share 100
2011-05-31 08:32:35 | Moo! Wrapper | URL http://moowrap.net/; Computer ID 1593; resource share 100
2011-05-31 08:32:35 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 5815304; resource share 100
2011-05-31 08:32:35 | Milkyway@home | General prefs: from Milkyway@home (last modified 05-May-2011 22:13:39)
2011-05-31 08:32:35 | Milkyway@home | Host location: none
2011-05-31 08:32:35 | Milkyway@home | General prefs: using your defaults
2011-05-31 08:32:35 | | Reading preferences override file
2011-05-31 08:32:35 | | Preferences:
2011-05-31 08:32:35 | | max memory usage when active: 1535.12MB
2011-05-31 08:32:35 | | max memory usage when idle: 2763.21MB
2011-05-31 08:32:35 | | max disk usage: 40.00GB
2011-05-31 08:32:35 | | (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
2011-05-31 08:32:35 | | Not using a proxy

---

AAD,

Is the HD4300 card not good enough for GPU processing?

I found out that the HD4300 is good enough for GPU processing. I can see ATI4 prog running. So case closed for the time being. Thanks for all help.

---

I found out that the HD4300 is good enough for GPU processing. I can see ATI4 prog running. So case closed for the time being. Thanks for all help.

Yes. I can see it in your result pages for your pc.
You're actually crunching with CPU AND GPU.
see here; http://moowrap.net/results.php?hostid=1593
In the last tab is the application.
Where it says "Distributed.net Client v1.02 (ati14)" its the GPU'.
"Distributed.net Client v1.02" is for CPU.
See the difference in timings!

aad,

It is a huge difference. I downloaded the latest driver and installed that one. I´m very satisfied with the result.

I moved the Einstein project to my other rig. Not that quick but still crunching.

Rgds
Bernt

---