Welcome to MilkyWay@home

Posts by Mad Matt

1) Message boards : Number crunching : Suddenly most results invalid (Message 51469)
Posted 22 Oct 2011 by ProfileMad Matt
Post:
If you look at the top computers you may notice that almost all of them regularly post invalid tasks. This is VERY unusual compared to other projects and may indicate either a problem with 0.82 or a validator problem. The former CP apps did not exhibit this behavior.


Affirmative when looking at my rigs.
2) Message boards : Number crunching : Problem with receiving credits (Message 51457)
Posted 21 Oct 2011 by ProfileMad Matt
Post:
Is this Linux-specific? On Windows I do not see problems with using the optimised app.
3) Message boards : Number crunching : Suddenly most results invalid (Message 51446)
Posted 19 Oct 2011 by ProfileMad Matt
Post:
I should add in hindsight, it could be some of those results have been coming from using wrong GPU clocks, but it's hard to track this back.

Since posting and since definitely using my regular OC settings, the problem has been solved for me.
4) Message boards : Number crunching : Suddenly most results invalid (Message 51310)
Posted 6 Oct 2011 by ProfileMad Matt
Post:
It looks like it has been fixed? First efforts today after a while:

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=312643
5) Message boards : Number crunching : Suddenly most results invalid (Message 51237)
Posted 27 Sep 2011 by ProfileMad Matt
Post:
Cheers for the feedback, Matt. At least I know now I don't have to start with turning the rig upside down.
6) Message boards : Number crunching : Suddenly most results invalid (Message 51231)
Posted 27 Sep 2011 by ProfileMad Matt
Post:
Host ID: 312643

I did not make any changes on OS, driver, hardware or app there (opt. 0.82). It's W7, ATI 0(not used)=5450, ATI 1 =4770, ATI Catalyst 11.3. Suddenly this rig almost went into validation nirvana. Just a few WUs still get validated.

Any ideas?
Cheers
7) Message boards : News : Make-Up Credits to Run Wednesday and Thursday (Message 50278)
Posted 20 Jul 2011 by ProfileMad Matt
Post:
Cheers for keeping this long-standing promise. To be honest, I already gave up on that. Good to see you made up your mind and found a better decision.
8) Message boards : News : testing a new search 'ps_test_1' (Message 48999)
Posted 25 May 2011 by ProfileMad Matt
Post:
I've had ps_test_4 passing correctly on two rigs now. Looks like all WUs made it.
9) Message boards : News : testing a new search 'ps_test_1' (Message 48977)
Posted 25 May 2011 by ProfileMad Matt
Post:
All erroring out here. NNT for now.

Since I won't become UOTD anyway for my charming posts: Wasn't there a roadmap saying a) get things stable b) tackle the lag if possible c) do the credit x2 thingy?

Hmm.
10) Message boards : News : ATI application updated to 0.60 (Message 48207)
Posted 24 Apr 2011 by ProfileMad Matt
Post:
Not sure what was happening now, but my output has gone down the drain, most likely because of inconclusive validations and also a good number of invalid validations. Is this linked to optimized apps settings or are there stock users concerned as well?
11) Message boards : News : ATI application updated to 0.60 (Message 48090)
Posted 21 Apr 2011 by ProfileMad Matt
Post:
@Assimilator1:

it should get better if you:
- report all finished MW tasks (assuming you're running 0.62 already)
- stop your BOINC
- place a file called "app_info.xml" in your MW folder with the following content:
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.62_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>62</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<cmdline>--gpu-target-frequency 60</cmdline>
<file_ref>
<file_name>milkyway_0.62_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


This will increase the target screen refresh time from 30 Hz to 60 Hz, which in my case is enough to make it almost smooth again. You can also adjust "<count>0.5</count>" to "<count>1</count>" if you want to run 1 WU at a time rather than 2 WUs at a time (as I'm currently doing to avoid the idle GPU time between WUs).
I don't expect you'd need to adjust polling with this.

MrS


Cheers, ETA. I tried this app_info, but in my case it did not really help. I found some odd values for tolerable lag:

4770 2 WUs at a time
5970 3-4 WUs (does not make a huge difference)
5870 4 WUs (2 and 3 WUs can show massive lag).

12) Message boards : News : ATI application updated to 0.60 (Message 47854)
Posted 14 Apr 2011 by ProfileMad Matt
Post:
I experienced that when crunching 2 WU's with 0.62 on two ATI 5870, looking to NASA-TV is no joy as the stream freezes a lot. Sound stay uninterrupted.
Not a big deal as I have more rigs to watch NASA. But with 0.23 I hadn't this experience.


I am having strange lag problems too when running 2 WUs at least:

Ati 4770x2: no lag at all
5870: strong lag running 2WUs, next to no response when running 3.
5970: notable lag running 2WUs per GPU.

All W7, CCC 10.10
13) Message boards : News : ATI application updated to 0.60 (Message 47836)
Posted 14 Apr 2011 by ProfileMad Matt
Post:
Cheers to Matt and Arkayn, awesome work these days!

PS: also using 10.10, I can only recommend since you can still downclock memory really well.
14) Message boards : News : ATI application updated again (Message 47561)
Posted 11 Apr 2011 by ProfileMad Matt
Post:
This is embarassing. I think the project would be better off if they just restored last week's version and our administrators backed off, took a few deep breaths and did some real software engineering and project planning.

If this were a release from a for-profit software company I would agree with you. Considering this is a volunteer science project run on a very tight budget I have to disagree.

There was an initial unplanned oops which took the project down and was going to necessitate a few days to recover. What better time to throw in the upcoming changes that might mess things up and take the project down for a few days? It also saves a lot of time and money avoiding all that pesky beta testing, scheduled roll outs and downtime. People tend to be more productive when they're under the gun. ;-)


It's a valid point. No matter if volunteer or not, this either slows the project down massively or cuts into resources for other projects if you decide to dedicate cores to keep the speed. On top, missing optimization increases losses by load/unload times of the GPUs. This means less work being done for MW and for other projects. No matter if you call this embarassing or not, it's far away from being any progress.
15) Message boards : Number crunching : app 0.57 100% core use... (Message 47521)
Posted 10 Apr 2011 by ProfileMad Matt
Post:
When will those new clients be rolled out? I am still seeing CPU usage from 75 to 100 percent here.




©2020 Astroinformatics Group