Welcome to MilkyWay@home

Posts by valterc

1) Message boards : Number crunching : R9 290 (Message 61849)
Posted 7 Jun 2014 by Profilevalterc
Post:
Yep, no success at all. This may work for 280 (but my one works without it, just with the Catalyst driver) but not for 290....
2) Message boards : Number crunching : R9 290 (Message 61847)
Posted 6 Jun 2014 by Profilevalterc
Post:
I recently got a R9 280-X and it works perfectly with MilkyWay (with the 14.4 driver). I also got a R9 290-X (Hawaii) and it doesn't work at all, MilkyWay claiming that it is a ATI GPU R600 (R38xx) which has no OpenCL support. However it HAS openCL support (Collatz works flawless, and also Gpu-Z confirms this), what it's missing is the CAL support... but anyway it doesn't work with Milkyway and I wanted to use it for this project (yes, I know all issues regarding bad DP performances).

Has anyone here had success running an Hawaii GPU? If yes, can you please share some hints?

3) Message boards : News : New MilkyWay Separation Modified Fit Runs (Message 60522)
Posted 5 Dec 2013 by Profilevalterc
Post:
I just checked the credit issue again and found the same behavior as a few weeks ago. Credit is fixed at 213.76 while runtimes vary considerably (on my HD7970) from ~55s (ps_modfit_15_3s_128wrap_3_1382698503_6716313_2) to ~85s (de_modfit_15_3s_bplmodfit_128wrap_1_1382698503_6587065_3).

4) Message boards : News : New MilkyWay Separation Modified Fit Runs (Message 60263)
Posted 31 Oct 2013 by Profilevalterc
Post:
I made some statistics on my 7970 http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=100828

MilkyWay@Home v1.02 (standard)
average runtime: 28.27, credit per day: 334,636.29

Milkyway@Home Separation (Modified Fit) v1.28 Here I get two different type of workunit, same credit and runtimes of ~84s or ~55s with the following figures
average runtime: 74.03, credit per day: 249,476.42
5) Message boards : News : Separation updated to 1.00 (Message 52943)
Posted 9 Feb 2012 by Profilevalterc
Post:
CAL 12.1, BOINC 6.10.60, 2x HD 6950, no app_info

I'm getting tons of work (mixed type, both v1.00 & v0.82). Everything is ok,
although the 1.00 wus are a little bit slower, say ~72sec instead of ~68s), is it normal?
6) Message boards : Number crunching : Validate Error (Message 52774)
Posted 2 Feb 2012 by Profilevalterc
Post:
In some cases the stderr from BOINC is truncated or missing completely. I think I mostly fixed the problem for future updates


I also have, sometime, this kind of error (empty stderr)
<core_client_version>6.10.60</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>
7) Message boards : News : Any remaining major credit or application problems? (Message 49539)
Posted 24 Jun 2011 by Profilevalterc
Post:
for me better not in the weekend (going around....)
8) Message boards : Number crunching : Bad WUs (Message 48740)
Posted 13 May 2011 by Profilevalterc
Post:
i just got two of them:

de_separation_10_3s_free_2_420330_1305301089_1
de_separation_10_3s_free_2_423122_1305301520_0

the stderr log is the following:

<core_client_version>6.10.60</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkywayathome_client separation 0.62 Windows x86 double CAL++ </search_application>
Found 1 CAL devices
Chose device 0

Device target:         CAL_TARGET_CAYMAN
Revision:              1
CAL Version:           1.4.900
Engine clock:          810 Mhz
Memory clock:          1100 Mhz
GPU RAM:               2048
Wavefront size:        64
Double precision:      CAL_TRUE
Compute shader:        CAL_TRUE
Number SIMD:           22
Number shader engines: 2
Pitch alignment:       256
Surface alignment:     4096
Max size 2D:           { 16384, 16384 }

Estimated iteration time 119.647166 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 4 chunks
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using { 1, 4 } chunk(s) of size { 1400, 400 }
Integration time = 82.015017 s, average per iteration = 128.148464 ms
Integral 0 time = 83.759557 s
Estimated iteration time 29.911792 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 1 chunks
Integration range: { nu_steps = 640, mu_steps = 400, r_steps = 1400 }
Using { 1, 1 } chunk(s) of size { 1400, 400 }
Integration time = 20.501572 s, average per iteration = 32.033706 ms
Integral 1 time = 20.980437 s
Likelihood time = 6.569375 s
Non-finite result
Failed to calculate likelihood
<background_integral> 0.000972832098789 </background_integral>
<stream_integral>  27.656173175642195  1183.863218271929800  -0.138228459499025 </stream_integral>
<background_likelihood> -2.983789565586555 </background_likelihood>
<stream_only_likelihood>  -58.146684859558270  -7.945487711078723  -1.#IND00000000000 </stream_only_likelihood>
<search_likelihood> -1.#IND00000000000 </search_likelihood>
18:19:23 (2796): called boinc_finish

</stderr_txt>

9) Message boards : Number crunching : Strange things on HD5970 (Message 46420)
Posted 3 Mar 2011 by Profilevalterc
Post:
Please be aware that 11.2 catalyst has some big problems (at least with the 5890)

I reinstalled a previous version and everything is running smoothly...
10) Message boards : Number crunching : Strange things on HD5970 (Message 46414)
Posted 3 Mar 2011 by Profilevalterc
Post:
Hi all,

starting from today I'm having results like this:

CAL Runtime: 1.4.1016
Found 2 CAL devices

Device 0: ATI Radeon HD5800 series (Cypress) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached)
GPU core clock: 1000 MHz, memory clock: 1500 MHz
1600 shader units organized in 20 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

Device 1: ATI Radeon HD5800 series (Cypress) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached)
GPU core clock: 1000 MHz, memory clock: 1500 MHz
1600 shader units organized in 20 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

...

WU completed.
CPU time: 26.5358 seconds,  GPU time: 92.3703 seconds,  wall clock time: 94.065 seconds,  CPU frequency: 2.80643 GHz

...

Validate state	Valid
Claimed credit	0.154616492621667
Granted credit	213.756235697696
application version	MilkyWay@Home v0.23 (ati13ati)


Now, two things look strange:

a) GPU core and memory frequencies are not the right ones, should be 780/850 according to Afterburner and GPU-Z
b) too much CPU time?
c) I'm also starting to have 'validate errors'....

this is the host http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=205229

Any hints about this?
Thank You
11) Message boards : Number crunching : Testing ATI Application Availability (Message 35671)
Posted 15 Jan 2010 by Profilevalterc
Post:
Thank you all for the hints about installing CAT 9.12 on XP x64, seems working and I am currently crunching (and better at all gettin valid results) MW workunits.

However it would be fine to have app_info availabile to fine tune the thing. I'm thinking mainly at the use of the 'w' parameter to reduce screen lag while I use this computer for work.

12) Message boards : Number crunching : Testing ATI Application Availability (Message 35644)
Posted 14 Jan 2010 by Profilevalterc
Post:
Well, I'm not able anymore to crunch MW workunits on ATI 4850.... I did it fine since a couple of days ago (using anonymous platform).

Now. I don't think it's a good idea to select CPU only tasks (getting some units to crunch with the GPU) in my preferences and micromanage the whole thing...

I also tried to restart BOINC without app_info.xml (this way loosing some important cmdline parameters) and all I got was

1/14/2010 11:58:10 AM	Milkyway@home	Message from server: No work sent
1/14/2010 11:58:10 AM	Milkyway@home	Message from server: ATI Catalyst 9.2+ needed to use GPU
1/14/2010 11:58:10 AM	Milkyway@home	Message from server: Your computer has no NVIDIA GPU


I run XP x64 with Catalyst 8.11 (wich is the best one to have on this OS).

Hope this will be solved somehow (switching to Collatz for the moment)
13) Message boards : Number crunching : my workunits are all marked invalid... (Message 34898)
Posted 29 Dec 2009 by Profilevalterc
Post:
just to let you know about this.
14) Message boards : Number crunching : Strange things happen (credit) (Message 32980)
Posted 3 Nov 2009 by Profilevalterc
Post:
well, look at this:

15) Message boards : Number crunching : Strange things happen (credit) (Message 32970)
Posted 3 Nov 2009 by Profilevalterc
Post:
All the work done yesterday, I mean all the credits gained yesterday, have beeen lost....
16) Message boards : Number crunching : GPU only running one wu at a time? (Message 32969)
Posted 3 Nov 2009 by Profilevalterc
Post:
better have <count> set to 0.5
17) Message boards : Number crunching : Milkyway not running... (Message 32611)
Posted 21 Oct 2009 by Profilevalterc
Post:
DA decided that GPU work should be done in strict FIFO order ... that means that if you want to run MW mostly you need to trim your queue to try to avoid large chunks of Collatz being DL. Of course, the issue here is that you have network drops and lowering the queue means you will run out of work ...

In that this would not solve your problem ... you need to complain on the alpha mailing list ... I have, but so far to silence ... What you really want is to have Collatz on hand and only run it if you cannot get MW work ... or you run dry because of a network outage ...

Theory says that Resource Share will be respected over time ... but I cannot prove that ... in that the debt calculations seem to have been bent for some time my suspicion is that this is also not true ...

I run with a one day something cache and right now my ATI system seems to run a day on MW if it can get work, then it will DL 90 or so Collatz and spend a day running them off ... then again, I also run with 100/100 share allocation so I am not quite in your situation...

Anyway, your problem is that you are running into one of the later brainstorms of UCB... oh, alternative, downlevel your installation and use app info to make it work (of course you may not be able to run CPU of MW and Collatz) ...



I already use app_info, in fact I have a set up that forces CPU only Seti & Primegrid and GPU only for MW & Collatz.

The only way I know for having some MW crunching is babysitting the whole thing and suspend Collatz from time to time....

Oh, btw, a couple of days ago I resetted both MW & Collatz after letting them run empty (no new tasks) but I still have the same bahavior....
18) Message boards : Number crunching : Milkyway not running... (Message 32601)
Posted 21 Oct 2009 by Profilevalterc
Post:
Hi all,

Shortly, this is my problem:

I would like to run Milkyway for most of the time and use Collatz as a backup project. I do have some network drops and it doesn't reconnect automatically so I really need a backup project.

My dual-core runs Collatz, SETI and Primegrid with resource share 100 and MW with resource share 700.

However, although the resoruce share is respected by the cpu only projects (SETI & Primegrid) it seems that is ignored by the ATI GPU only projects. Collatz is running almost all the time....

Any hints?

BTW, I use client v6.10.13, all but Primegrid with app_info. No problems at all crunching, ie no errors, just the resource share problem. Boinc connects every 0.1 and has an additional work buffer of 4 days.
19) Message boards : Number crunching : 6.10.1 Posted. (Message 30376)
Posted 8 Sep 2009 by Profilevalterc
Post:
maybe a little off topic... but, what is the meaning of the two lines

ignoring unknown input argument in app_info.xml: --device
ignoring unknown input argument in app_info.xml: 0

that started appearing in stderr after upgrading to 6.10.3?
20) Message boards : Number crunching : ATI GPU app 0.19f fixes the ps_sgr_208_3s errors (Message 30117)
Posted 2 Sep 2009 by Profilevalterc
Post:
Sorry for bothering you about this but ... do you know how would it possible for me (having a dual core and 1 gpu) to set up boinc or the app_info files in order to have MW WUs running all the time and at least one core crunching a CPU application?

currently crunching MW (400% share) PrimeGrid(200) and SETI AP (100)

thank you all for any hints


Next 20

©2019 Astroinformatics Group