Welcome to MilkyWay@home

Posts by [AF>DoJ] supersonic

1) Message boards : Number crunching : ATi 4770 - Problems with Milkyway (Message 32674)
Posted 23 Oct 2009 by Profile[AF>DoJ] supersonic
Post:

You need to be running the latest Gipsel app under the anonymous platform mechanism and using the supplied app_info.xml.
In this file, edit <cmdline></cmdline> to read

<cmdline>w1.3</cmdline>

for each time it occurs. Make sure you stop and restart BOINC.

Read the readme.txt file that came with the package as many times as you need to understand the various options and what they do. You need to read it carefully from end to end. There are other useful options as well.


thanks for this. As I don't have a win7 yet, I'll have to manage with XP32

I tried the 9.8 no CCC, and the <cmdline>w1.3</cmdline> part.

gpuZ tells me the card is loaded at 80%

It is stable as long as I do not touch anything, open no window, launch no program...
2) Message boards : Number crunching : ATi 4770 - Problems with Milkyway (Message 32646)
Posted 22 Oct 2009 by Profile[AF>DoJ] supersonic
Post:
...
3) Message boards : Number crunching : ATi 4770 - Problems with Milkyway (Message 32645)
Posted 22 Oct 2009 by Profile[AF>DoJ] supersonic
Post:
4) Message boards : Number crunching : Using the MW ATi application, Q & A (Message 32641)
Posted 22 Oct 2009 by Profile[AF>DoJ] supersonic
Post:

thanks for these, verstapp

5) Message boards : Number crunching : Using the MW ATi application, Q & A (Message 32639)
Posted 22 Oct 2009 by Profile[AF>DoJ] supersonic
Post:
Hello,


Q) What is the most common configuration in terms of OS/ATi Catalyst/BOINC/ATI app used?

A common trend is the two configurations listed below:

XP / Cat 8.12 / BOINC 6.4.7 / 0.19f
XP / Cat 8.12 / BOINC 6.6.20 / 0.19f


I guess this is not accurate anymore

anyway, I have a 4770 and Cat 8.12 does not recognize the 4770


I encounter VPU recovery after a few seconds of calculation.

I'm on XP32 / CCC 9.9 / Boinc 6.10.13 / 0.20b (tried also the 0.20)

anyone for a clue ?

thanks
6) Message boards : Number crunching : Work Availability v2 (June 9) (Message 24793)
Posted 10 Jun 2009 by Profile[AF>DoJ] supersonic
Post:
a rushing river of WUs without the help of a script.

that's nice !

thanx
7) Message boards : Number crunching : ATI GPU app 0.19f fixes the ps_sgr_208_3s errors (Message 24360)
Posted 6 Jun 2009 by Profile[AF>DoJ] supersonic
Post:

thanks a lot, nice job !
8) Message boards : Number crunching : Work Availability? (Message 24149)
Posted 4 Jun 2009 by Profile[AF>DoJ] supersonic
Post:

since the last 2 or 3 days now, I'm getting a little more WUs

the idling time of my ATIs is shorter now.

...

I'm surprised this 1 min setting has an impact.
It means a lot of scripters were refreshing more than once in a minute...
9) Message boards : Number crunching : Why is it so hard to get work? (Message 23487)
Posted 27 May 2009 by Profile[AF>DoJ] supersonic
Post:
As I pointed out in this message and to Travis...

To stop the scriptors hitting the project so hard, you could increase the minimum time between host contacts at the server end. LHC@home increased theirs to just over 15 minutes....maybe you could try 2 minutes and see what happens. I believe it is a simple server side setting.



I agree with this 15 minute minimum time between host contact...

As a script user, if I decide to stop running script, the whole project wins a little, and I loose a lot (compared to those still running script).

It would be better that every scripter stops, so that we'll all win.

But that won't happen as we're greedy humans.

That's why I won't stop running script.

But as I see it hammers the server, I see as an easy solution to set a 15 minute (or watever) minimum time between host contact

...

Brian Silver's analogy with grocery behavior is very accurate.

We live a starvation time

Every body wants bread, but there is very little amount of baguettes available.

A fight is close to occur if no rule is established to limit the maximum number of baguettes a good mother can bring back to feed her hungry childs.
10) Message boards : Number crunching : MilkyWay_GPU - Almost There! (Message 22917)
Posted 21 May 2009 by Profile[AF>DoJ] supersonic
Post:
much respect to your involvement, CP.

and may the code be cristal clear ;)
11) Message boards : Number crunching : WUs distribution (Message 21472)
Posted 7 May 2009 by Profile[AF>DoJ] supersonic
Post:

Of course, the easy way to stop the hammering of the server would be to reduce the credits to that of *cough*seti*cough*, or even below that. Then watch how quickly people will stop crunching and hammering here - after some very unpleasant postings in the forum, no doubt.


I'm sure CPU guys are not hammering as much as we GPU guys do.

Therefore it's a false good idea.

A better solution would be to implement a SETI-ATI-app, and you'll see GPU-guys move away for a fresh source of credit, MW could breath again after that...



I read that Cluster physik developped the MW-ATI-app, could it be possible to reiterate this achievement ?




.
12) Message boards : Number crunching : Why is it so hard to get work? (Message 20902)
Posted 30 Apr 2009 by Profile[AF>DoJ] supersonic
Post:
I am just getting tired of all these people saying, go to other projects until this is resolved.
If I were running the CPU app that is a valid comment. But since alot of people (such as myself) only really run it on the GPU, that is not really an option.
I already run other projects on my CPU(s).
I just do not understand how some people here are still getting 60-100K a day when there are many more others that are barely getting anything. That is what is ticking me off.

I also keep reading about how they are working on a CUDA app, why not get the ATI one working first? Take on one thing at a time. There are other projects that are running under CUDA, this is the only one (recognized by BOINC) that runs under ATI.



I agree on that.

My feeling is that MW people are headed in a tough way of developping a new CUDA compatible project.

During that time, why not take the opportunity of Cluster Physiks's gifted people to create a new ATI app for GPU project ?

Then, when CUDA app is ready, both Nvidia and ATI can crunch.
13) Message boards : Number crunching : MilkyWay_GPU (Message 18830)
Posted 15 Apr 2009 by Profile[AF>DoJ] supersonic
Post:

GREAT !

\o/

hoping 1000 times long WUs
14) Message boards : Number crunching : Server Updates and Status (Message 17426)
Posted 3 Apr 2009 by Profile[AF>DoJ] supersonic
Post:
like spoiled rich kids.


...

I'm not jealous because some crunchers use v8 or v16 or even can have acces to server farms and 32 core machines...

I only have a c2d and it's OK that these people are in the same score table than me
I can compare with other similar cpus.

I once was top 22 in rac with my Q6600 on Rosetta. Shortly after came some 45 nm new cpus, and numerus 8 cores... now i7.
I sunk below top 1000 in rac, as did a lot of Q6600 that can be considered now "not so young" tools.

But I don't feel i7 should have had a special credit table and rankings.

Now, life evolves, new tools are available, and that's great ! If we create separate rankings, why not do the same for optimzed/standard apps, linux/win/mac, 2/4/8/16 cores ...

The fact is that GPU are better tools now. Maybe that will last only a few years, who knows ? It was hardly predictable last year that ATI's will be so effective crunchers.

That's why I think Milkyway People should not create two separate projects, but only a way to crunch longer WUs.
15) Message boards : Number crunching : Server Updates and Status (Message 17378)
Posted 2 Apr 2009 by Profile[AF>DoJ] supersonic
Post:

boinc 6.8 will detect ATIs
16) Message boards : Number crunching : Server Updates and Status (Message 17375)
Posted 2 Apr 2009 by Profile[AF>DoJ] supersonic
Post:
furthermore, CPU's can be useful on projects that didn't implement GPU crunch yet

don't split stats !
17) Message boards : Number crunching : Server Updates and Status (Message 17343)
Posted 2 Apr 2009 by Profile[AF>DoJ] supersonic
Post:
I'd suggest the GPU project spit out normal (but longer, more complex) WUs that would run on CPUs, and it's up to us to use the correct GPU specific app.


I agree on that




©2021 Astroinformatics Group