PDA

View Full Version : Milkyway: Separation updated to 1.00



RSS
02-08-12, 12:45 PM
I've updated all of the separation applications to 1.00. For changes people might care about,
- The old CAL version is gone; it's replaced with the OpenCL application. On AMD/ATI GPUs (older than 79xx) it is using some hackery to use the same IL kernel as before so it should be as fast. However this also means the Radeon 38xx cards aren't supported with new stuff.- Radeon 79xx stuff should work- The occasional validate errors from empty / truncated stderr should stop- AVX will be used if available on Linux and Windows (64 bit only for Windows)- I've increased the default GPU target frequency so GPU stuff should make things less laggy on average. You can now also configure this with the web preferences now so you don't need to use app_info stuff if you want to play with that.- Partial workaround with high CPU usage with recent Nvidia drivers. It should cut down on the CPU usage a bit while not sacrificing too much. There are options to change the polling mode if you want to lower the CPU usage further while not slowing it down. (--gpu-wait-factor and --gpu-polling-mode work similarly to how they did with the old CAL one, but slightly different)

As usual post problems you run into here.

More... (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2764)

coronicus
02-09-12, 12:20 AM
This sound good anyone try it out yet im hoping it does well but sad to see my 3850 will no longer work.

Al
02-09-12, 07:39 AM
This sound good anyone try it out yet im hoping it does well but sad to see my 3850 will no longer work.

Yeah, I noticed one. It won't dowload tasks for my 6950 now. I have another project I'm working on today so I won't be able to try upgrading drivers till late.

Fogle
02-09-12, 08:12 AM
I have a ATI 4770, & a 5830 in one box and can't download any WU's. :mad: I have to go to work so it's over to Colitz for now, but really want to push Milkyway. Hopefully this will be an easy fix? :confused:

trigggl
02-09-12, 09:10 AM
I guess it's too much to ask to make these testing apps before forcing them on everybody.

Al
02-09-12, 09:40 AM
Yeah, I noticed one. It won't dowload tasks for my 6950 now. I have another project I'm working on today so I won't be able to try upgrading drivers till late.

Well, no explanation....but my 6950 just started downloading tasks again...but run times have quadrupled. Wow, that's an improvement.:mad:

99276471 76641799 9 Feb 2012 | 13:18:01 UTC 9 Feb 2012 | 14:37:46 UTC Completed and validated 278.84 6.80 159.86 MilkyWay@Home v1.00 (opencl_amd)
98882741 76362330 8 Feb 2012 | 18:05:21 UTC 8 Feb 2012 | 19:37:27 UTC Completed and validated 68.39 9.16 159.86 MilkyWay@Home v0.82 (ati14)

coronicus
02-09-12, 09:42 AM
wow that is so not good... expected it to be a little more but that is just insanely bad.

I had already set moo to no new task but i got a day or so worth of crunching to finish them off but after seeing that i might be loading up the wu for moo again ugh... once i get a chance ill suspend moo and see what mw does on my 6950.

Al
02-09-12, 09:58 AM
wow that is so not good... expected it to be a little more but that is just insanely bad.

I had already set moo to no new task but i got a day or so worth of crunching to finish them off but after seeing that i might be loading up the wu for moo again ugh... once i get a chance ill suspend moo and see what mw does on my 6950.

I do get a mix of 82 (ati) tasks and the new 100 (Opencl) tasks. The ati still maintain the fast times and Opencl contines to suck. You can't change it in the preferences.

Fire$torm
02-09-12, 11:09 AM
I do get a mix of 82 (ati) tasks and the new 100 (Opencl) tasks. The ati still maintain the fast times and Opencl contines to suck. You can't change it in the preferences.

This is proof as to how bad OpenCL is.... This sucks goats nuts......

trigggl
02-09-12, 01:57 PM
Now that I've gotten (before it crashed) the 4870 to crunch the new tasks, my run times went from 2:38 to 2:28.

[off topic rant]I think the latest Linux kernels are buggy. Whenever I try to run 3.1 or 3.2, the video crashes within 24 hours. Now I'm stuck at work and the crash even affects my ability to reboot. I tried to reboot and it never came back up. So, it's probably still on with one core at 100% doing nothing. I have to physically turn the computer off to recover. Then it has to fix hard drive errors and reboot again. This is one of the reasons I keep boinc on its own partition.[/off topic rant] :mad:

coronicus
02-10-12, 12:46 AM
99993715 77216998 352929 10 Feb 2012 | 4:50:35 UTC 10 Feb 2012 | 5:31:51 UTC Completed and validated 62.09 3.06 159.86 MilkyWay@Home v1.00 (opencl_amd)
99992313 77215985 352929 10 Feb 2012 | 4:49:29 UTC 10 Feb 2012 | 5:30:44 UTC Completed and validated 63.09 3.07 159.86 MilkyWay@Home v1.00 (opencl_amd)

Windows 7 64bit AMD 12.1 driver 6950 unlock shader but no OC

So not sure why your times are so much slower

Al
02-10-12, 08:38 AM
Not sure either, but its not the only issue with that box. My 560ti 448 core was matching my 570s on DiRT times, but now those times have tripled. Neither of these cards are downclocking in any way that can be seen (gpu-z), aside from actual run times.

coronicus
02-10-12, 09:18 AM
Not sure either, but its not the only issue with that box. My 560ti 448 core was matching my 570s on DiRT times, but now those times have tripled. Neither of these cards are downclocking in any way that can be seen (gpu-z), aside from actual run times.

oh my something aint right... maybe not enough ram for the projects your running just a guess, not sure whatcha got running on the cpu end but i know i had that happen to one of my boxes with the nvdia/amd/cpu mix ran some project from wcg that used allot of memory and the system came to a crawl.

Al
02-10-12, 11:17 AM
That could be the problem. I have all 4 cores running WCG on a Q6600 with 4GB of RAM, along with mw on my 6950 and DiRT on the 560. I'll free up a couple of cores and see if that fixes it.

Al
02-10-12, 08:18 PM
Nope, didn't fix it. I rebooted and mw ran fine for a couple of minutes then screen blanked and then came back on. Not showing any downclocking and both the 6950 and the 560 slowed down to a crawl. Suspended mw, rebooted again. Enabled collatz on the 6950, all 4 cores and DiRT on the 560....no problem. :confused:

I'm downloading the newest ATI drivers to see if that helps unless anyone has a better idea.

Al
02-11-12, 10:31 AM
New drivers didn't help either. Runs like a champ until you re-enable. Mw, then the Gpu resets. The last time I got an error message that stated that and that the card was no longer following commands...or something to that effect. Looked at the mw boards and couldn't see where anyone else was having a similar problem.

I'll try backing the drivers up to 11.9 and see if that works. If not I'll post the problem on the mw boards.

coronicus
02-11-12, 06:58 PM
New drivers didn't help either. Runs like a champ until you re-enable. Mw, then the Gpu resets. The last time I got an error message that stated that and that the card was no longer following commands...or something to that effect. Looked at the mw boards and couldn't see where anyone else was having a similar problem.

I'll try backing the drivers up to 11.9 and see if that works. If not I'll post the problem on the mw boards.

Well what i though was working fine on my end crashed out MW locked up the machine and lost a ton of work so something is up with it going back to moo.. ugh really wanted mw to stabalize but ugh oh well..