1)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2387)
Posted 23 Jan 2012 by Dan Post: Last night I crunched a bunch of Wus in 1 hour 20 minutes and see the dnetc-gpu-1.3 file has the processor priority at 9, so I cannot do anything. Sorry, I thought I posted this morning that I've fixed my problem and am back to 20 minute runs. I just needed to set the core in the 1.3 preferences to #3. Funny I didn't see that earlier, has it been there all the time. Thanks for the help. Dan |
2)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2371)
Posted 22 Jan 2012 by Dan Post: Well I tried this. Uninstall ATI drivers. Detach all boinc projects. Unistall boinc. Delete C:/ProgramData/Boinc Install ATI drivers. Install Boinc. Attach to Moo. Still same. I have 13 million till my 100 million mark. I guess I'm limping into home :-( |
3)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2369)
Posted 22 Jan 2012 by Dan Post: He is still running version 11.11 of the drivers, aren't they still not good for crunching and shouldn't he be at 11.9 or less right now. I went back to 11.9. Still the same Moo times. |
4)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2354)
Posted 21 Jan 2012 by Dan Post: Went back a version in the drivers to 11.11 still the same other projects like collatz and milkyway are taking the normal amount of time. It's just Moo on my two ATIs that is running real slow. I didn't start changing stuff until today, so I have no clue what the problem is. |
5)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2351)
Posted 21 Jan 2012 by Dan Post: Thanks. I'm not sure what happened. I detached/attached and everything seems to be running at the right rate. Never mind. It started out fast, but is now taking 1.5 hours. I've also reinstalled the ATI drivers. |
6)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2350)
Posted 21 Jan 2012 by Dan Post: Thanks. I'm not sure what happened. I detached/attached and everything seems to be running at the right rate. |
7)
Message boards :
Number crunching :
Runtimes with 1.3 version
(Message 2346)
Posted 21 Jan 2012 by Dan Post: I've seen my runtimes go from 20 minutes to 1.5 hours with the new 1.3 version. Running Win 7 x64, two 5870s. Mucked with which core, app_info.xml, etc and still the same performance |
8)
Message boards :
News :
Switched to granting static credit
(Message 282)
Posted 12 May 2011 by Dan Post: Actually if you look at thoughput, Milkyway and Collatz are getting me 2.3 credits per wall clock second per GPU. From Moo I get 1.9. From DNET as was said I'd 8 |
9)
Message boards :
News :
Switched to granting static credit
(Message 278)
Posted 12 May 2011 by Dan Post: What! I'm running dual 5870s. 2240 CR for 10 minutes of my cards time is less than other ATI projects and 1/4 of the old DNET. I noticed your work units out have dropped by 1/3 from this time yesterday. People let you use their hardware for credits. |
10)
Message boards :
News :
Switched to granting static credit
(Message 273)
Posted 12 May 2011 by Dan Post: Bye Moo! This change is the final nail in Moo's coffin. The credits are not worth it. Milkyway and Collatz are much better. I've read a lot of people today who are dropping Moo. You never even got close to DNet on credits. Why don't you give it up and let someone who wants to get people to do the work. MOO SUCKS! |
11)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 253)
Posted 12 May 2011 by Dan Post: I tried with CF on and CF off. Even took one card out. Until I set the core to 3 in Moo Wrapper perferences here it always took one hour+. Dan |
12)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 242)
Posted 11 May 2011 by Dan Post: Ok, I figured it out. I did the check for core performance. It came back saying core 3 was best. I tried changing the config using the local app, but that didn't work. When I set my core 3 in my Moo Wrapper preferences, my times for dual 5870s went to 9 minutes. 12 to 13K. But it's running real hot, 87C. I dropped the clocks to stock. |
13)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 240)
Posted 11 May 2011 by Dan Post: Ok, I figured it out. I did the check for core performance. It came back saying core 3 was best. I tried changing the config using the local app, but that didn't work. When I set my core 3 in my Moo Wrapper preferences, my times for dual 5870s went to 9 minutes. Thanks, Dan |
14)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 226)
Posted 11 May 2011 by Dan Post: I tried running the benchmark and setting the core to the best in the benchmark. It made no difference in my time. I'm getting 1 to 1.5 credits per second per GPU. Milkyway and Collatz get about 2.3 credits per second per GPU. I forget what dnet got but I know that it was much more than Milkyway or Collatz. Dan |
15)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 223)
Posted 10 May 2011 by Dan Post: I set those computers into diffrent groups and it helped bring the 1.2hr job down to 22mins on a ATI 5850 computer running stock speeds on both CPU and GPU. Single GPUs are taking about 10 to 15 minutes. 5870s in CF should be taking about 6 to 8 minutes. See times at the beginning of this thread. Dan P.S. I did update the CF profile (11.4) from ATI and saw my GPU go from ~5000 seconds to 3,000 seconds and my CPU drop to 1,600 seconds. |
16)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 221)
Posted 10 May 2011 by Dan Post: Ya. I'm still taking an hour+ on dual 5870s. P.S. I am running 1.01 |
17)
Questions and Answers :
Windows :
Multi-GPU task takes longer than single-gpu task
(Message 218)
Posted 10 May 2011 by Dan Post: Did anyone figure out the Dual GPU problem? I've had to abandon this project because the credits are so low for my two 5870s. |