Welcome to MilkyWay@home

Posts by PDelgado

1) Message boards : Number crunching : nVidia driver 275.33 (Message 50577)
Posted 7 Aug 2011 by PDelgado
Post:
Interesting. On mine I don't think it used any more CPU and didn't get any downclocking, but GPU utilization is a straight line at 97-98% with 266.58 but a zig-zag in the 40-50% range and took twice as long to complete with 275.33.
2) Message boards : Number crunching : nVidia driver 275.33 (Message 50567)
Posted 7 Aug 2011 by PDelgado
Post:
I tried 275.33 a few weeks ago and the performance is terrible with MW. They work OK with Seti opti apps, but MW apps haven't been updated to work with CUDA v4. You need to roll back to 26x.xx drivers, don't think any of the 27x.xx drivers will work well with the current MW apps.
3) Message boards : News : Separation updated to 0.82 (Message 49580)
Posted 25 Jun 2011 by PDelgado
Post:
I'm running an nvidia GTS450 and tried updating the drivers to the latest WHQL release, 275.33, hoping 0.82 had taken CUDA V4 into account. SETI liked the new drivers, MW not so much. My crunch times doubled yet MSI Afterburner didn't show downclocking, just erratic GPU utilization averaging about 50%.

Are there any work arounds or do we nvidia folk have to stick to the older 266.58 drivers?
4) Message boards : News : ATI application updated to 0.60 (Message 47830)
Posted 14 Apr 2011 by PDelgado
Post:
I'm working on setting it to require 11.3 (unless somebody has it reported working with something earlier).

Running 10.12 on AMD, Win7-64, 5850 with the app working and no invalids/errors. Haven't had any driver problems with any of the 57/59/60/62 versions. Tried 11.x before and found that on my system 10.12 is more stable than 11.x. My only problem seems to be an unrelated app/cc/bm scheduling thing that sometimes sends all MW work into immediate EDF mode.
5) Message boards : News : ATI application updated again (Message 47631)
Posted 11 Apr 2011 by PDelgado
Post:
... obviously the situation isn't ideal b/c i have to edit the cc_config.xml file and restart BOINC every time i want to switch from MW@H to S@H or vice versa ...

Did something related a while back switching cc_config back and forth for logging purposes. Can't find the files I used, but IIRC I wrote a couple of batch files that would suspend the projects, copy over the cc_config, force a re-read of cc_config, and resume the projects.

It went something like this: wrote two text files that were the cc_config files, called them something other than cc_config, wrote two batch files that would suspend, force copy the proper new cc_config, force a re-read, then resume. That way with a click of a shortcut on my desktop I could perform the switch.

I used, again IIRC, the boinccmd tool with the --project and the --read_cc_config operators. All the info is in the Boinc wiki. Good luck if you decide to try it.

http://boinc.berkeley.edu/wiki/Boinccmd_tool
6) Message boards : News : ATI application updated again (Message 47554)
Posted 11 Apr 2011 by PDelgado
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. ;-)
7) Message boards : News : ATI application updated again (Message 47544)
Posted 11 Apr 2011 by PDelgado
Post:
The new app takes care of the CPU over utilization, thank you. It doesn't hammer the GPU as hard as 0.23 did resulting in a little longer run time, but a more responsive system and a cooler card. Fair trade off, I even think it's better for a non-dedicated cruncher.

I'm still having the problem with the app bullying and beating its way to the top of the queue mentioned in post 47501. I enabled <coproc_debug> and following is a snip of the output. Any ideas?

4/10/2011 9:55:03 PM | SETI@home | [coproc] Assigning ATI instance 0 to 17fe11ac.25226.11519.15.10.5_0
4/10/2011 9:55:03 PM | SETI@home | Restarting task 17fe11ac.25226.11519.15.10.5_0 using setiathome_enhanced version 610
4/10/2011 9:55:06 PM | Milkyway@home | Sending scheduler request: To fetch work.
4/10/2011 9:55:06 PM | Milkyway@home | Reporting 1 completed tasks, requesting new tasks for ATI GPU
4/10/2011 9:55:07 PM | Milkyway@home | Scheduler request completed: got 1 new tasks
4/10/2011 9:55:09 PM | Milkyway@home | [coproc] Assigning ATI pending instance 0 to de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:55:09 PM | SETI@home | [coproc] ATI device 0 already assigned: task 17fe11ac.25226.11519.15.10.5_0
4/10/2011 9:55:10 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:55:10 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_10_3s_fix10_1_500170_1302486546_1
...
  >> This line repeats several hundred times <<
...
4/10/2011 9:55:10 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:55:10 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:55:10 PM | Milkyway@home | Starting de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:55:10 PM | Milkyway@home | Starting task de_separation_10_3s_fix10_1_500170_1302486546_1 using milkyway version 59
4/10/2011 9:55:38 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:56:09 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:56:25 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:57:25 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:57:38 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:58:09 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:58:25 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:58:32 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:58:55 PM | Milkyway@home | [coproc] ATI instance 0: confirming for de_separation_10_3s_fix10_1_500170_1302486546_1
4/10/2011 9:59:01 PM | Milkyway@home | Computation for task de_separation_10_3s_fix10_1_500170_1302486546_1 finished
4/10/2011 9:59:01 PM | SETI@home | [coproc] Assigning ATI instance 0 to 17fe11ac.25226.11519.15.10.5_0
4/10/2011 9:59:01 PM | SETI@home | Restarting task 17fe11ac.25226.11519.15.10.5_0 using setiathome_enhanced version 610
4/10/2011 9:59:03 PM | Milkyway@home | Sending scheduler request: To fetch work.
4/10/2011 9:59:03 PM | Milkyway@home | Reporting 1 completed tasks, requesting new tasks for ATI GPU
4/10/2011 9:59:04 PM | Milkyway@home | Scheduler request completed: got 1 new tasks
4/10/2011 9:59:07 PM | Milkyway@home | [coproc] Assigning ATI pending instance 0 to de_separation_13_3s_free_1_500595_1302486884_1
4/10/2011 9:59:07 PM | SETI@home | [coproc] ATI device 0 already assigned: task 17fe11ac.25226.11519.15.10.5_0
4/10/2011 9:59:07 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_13_3s_free_1_500595_1302486884_1
4/10/2011 9:59:07 PM | Milkyway@home | [coproc] Assigning ATI instance 0 to de_separation_13_3s_free_1_500595_1302486884_1
...
  >> And the process repeats for every WU <<

8) Message boards : News : ATI application (v0.57) should be available now (Message 47501)
Posted 10 Apr 2011 by PDelgado
Post:
New twist. This system does primarily Seti, but after the first few MW WU's processed normally, everyone after that starts immediately in high priority mode. Could be my version of Boinc Manager, could need a reboot, etc. Can't start troubleshooting right now so I'll just set NNT till I have more time.

After setting NNT for a while then resuming it displays the same behavior. The first few tasks run normally, then every MW task starts running in panic mode as soon as it is downloaded, even though the scheduling priority shows -16229.

I tried upgrading to the latest beta of Boinc Manager, but it shows the same behavior. Anybody else running multiple ATi projects having this problem?

Just glad I don't work at the RPI computer lab this week :-))
9) Message boards : News : ATI application (v0.57) should be available now (Message 47379)
Posted 10 Apr 2011 by PDelgado
Post:
New twist. This system does primarily Seti, but after the first few MW WU's processed normally, everyone after that starts immediately in high priority mode. Could be my version of Boinc Manager, could need a reboot, etc. Can't start troubleshooting right now so I'll just set NNT till I have more time.
10) Message boards : News : ATI application (v0.57) should be available now (Message 47365)
Posted 10 Apr 2011 by PDelgado
Post:
Yay, just did my first WU in a few days, and these are my observations on the new app so far. Not to be taken as a complaint, just reporting perceived differences on my 5850, AMD 600e, Cat. 10.12 drivers, Win7-64.

It does take longer than the 0.23 opti app I was using. It doesn't load the card as much as 0.23 did either, it ran about 75% utilization on the first one and about 50% on the second one. I had to use command line parameters to slow down 0.23 to 91%. Before the tasks ran in 115 to 160 seconds, while the small sample on the new app ran from about 140 to 270 seconds.

CPU utilization is a different story. Before it was barely noticeable, using about 12-20 secs. per WU, now it utilizes half a core for the duration of the WU, about 58-130 secs.
11) Message boards : News : Old ATI applications deprecated (Message 47268)
Posted 9 Apr 2011 by PDelgado
Post:
Is the optimized 0.23 app currently hosted on Arkayn's site one of the deprecated ones, or is it still good?

It's one of the apps that has been deprecated.

Thanks. At least I don't have to clear out my cache before resetting the project. :-)
12) Message boards : News : Old ATI applications deprecated (Message 47263)
Posted 9 Apr 2011 by PDelgado
Post:
Is the optimized 0.23 app currently hosted on Arkayn's site one of the deprecated ones, or is it still good?
13) Message boards : News : bad news (Message 47261)
Posted 9 Apr 2011 by PDelgado
Post:
I would kill the guy who is responsible for this :P
about 1 million results was simply burned in the oven?!
such a waste =(
That would mostly be my fault

I see this more as a "demonstration experiment". All the posts I've seen with people asking why we can't have large WU caches can now clearly see the reason. :-)
14) Message boards : Number crunching : nVidia GPUs and double precision (Message 46340)
Posted 22 Feb 2011 by PDelgado
Post:
Take a look at the CUDA wiki page, and a couple of screens down you will see a table with the compute capability of the more popular card families. Anything with a compute capability of 1.3 or higher will do doubles.
15) Message boards : Number crunching : GTS 450 GPU (Message 46254)
Posted 16 Feb 2011 by PDelgado
Post:
Glad to hear it worked for you also. Don't know if it's all the Fermi cards or only the GTS450 but they just don't like the stock app, or maybe the stock app doesn't like them. :-)
16) Message boards : Number crunching : GTS 450 GPU (Message 46232)
Posted 14 Feb 2011 by PDelgado
Post:
I posted something similar in a different thread a few minutes ago. I'm also running Win7 with a GTS450 and received a few errors with the stock 0.52 Open_CL app. I switched to the 0.24_CUDA optimized app and haven't had any errors since.
17) Message boards : Number crunching : GPU Requirements [OLD] (Message 46230)
Posted 14 Feb 2011 by PDelgado
Post:
It should work fine, lets try the Non Open_CL app and see if that works.

http://www.arkayn.us/milkyway/MW_0.24_CUDA.zip

Just an FYI. I just got a GTS450 also with the latest drivers (266.58) and had several errors with the stock Open_CL app, maybe about 20%. Now with the 0.24_CUDA app no errors, and not sure but the processing times may have improved slightly. Any idea where I can get a Win7_64 AMD SSE3 optimized app?




©2020 Astroinformatics Group