Welcome to MilkyWay@home

Separation updated to 1.00

Message boards : News : Separation updated to 1.00
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 · Next

AuthorMessage
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53054 - Posted: 10 Feb 2012, 21:36:41 UTC

....When .82 no longer works, unless things are fixed, I will be 'MW-less'.


That will be increasingly common story with 4XXX as the year moves on as 4XXX have limited OpenCL support. Matt has done some sterling tweeks in the background to get this going here for 4XXX, but the longer term prognosis re 4XXX and OpenCL across BOINC is one of gradual degrading as full blown OpenCL takes hold across BOINC, as a consequence of the dropping of CAL by AMD.

Not happening "by yesterday", but it will happen, and its irreversable

Regards
Zy
ID: 53054 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Bymark
Avatar

Send message
Joined: 6 Mar 09
Posts: 51
Credit: 492,109,133
RAC: 0
Message 53055 - Posted: 10 Feb 2012, 21:40:10 UTC - in response to Message 53053.  

The other thing to note, with the earlier BM (6.10.58 or 6.12.32) which do get work with the 11.8 Catalyst -- they get .82 separation work units -- which process fine.


I think the 7.0.8 BM 'wants' the 1.0 separation work units with OpenCL, but MW doesn't 'like' this.

The deal here which might be interesting, POEM GPU *requires* the BOINC 7.x series (and seems picky about sub versions there), and runs an OpenCL application there.

So at the moment, I have an either/or -- POEM GPU or MW GPU. I don't run much for POEM GPU (it is new for those guys and so has some issues AND is a CreditNew (bad, bad) house these days.

Also, as long as .82 separation works with work units I will be OK for now on all the 6.10.58 and 6.12.32 BM + 11.8 Catalyst combinations I have deployed. When .82 no longer works, unless things are fixed, I will be 'MW-less'.


The other thing to note, with the earlier BM (6.10.58 or 6.12.32) which do get work with the 11.8 Catalyst -- they get .82 separation work units -- which process fine.

Nopem, do not, errors out running on xp 32......
ID: 53055 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 1 Sep 08
Posts: 520
Credit: 302,524,931
RAC: 15
Message 53056 - Posted: 10 Feb 2012, 21:41:30 UTC - in response to Message 53054.  

Fair enough, when it happens, I'll process elsewhere -- new double precision AMD cards are quite an expense, and also, from what I've seen require more power as well. I'm not inclined to rebuild a batch of systems for that purpose. When other projects also move to OpenCL -- I'll probably shut down my BOINC work as I simply can't justify that sort of investment in time for the projects.


....When .82 no longer works, unless things are fixed, I will be 'MW-less'.


That will be increasingly common story with 4XXX as the year moves on as 4XXX have limited OpenCL support. Matt has done some sterling tweeks in the background to get this going here for 4XXX, but the longer term prognosis re 4XXX and OpenCL across BOINC is one of gradual degrading as full blown OpenCL takes hold across BOINC, as a consequence of the dropping of CAL by AMD.

Not happening "by yesterday", but it will happen, and its irreversable

Regards
Zy


ID: 53056 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 1 Sep 08
Posts: 520
Credit: 302,524,931
RAC: 15
Message 53057 - Posted: 10 Feb 2012, 21:42:57 UTC - in response to Message 53055.  

Works OK here for me as I reported -- no big deal though, a lot of variables in the mix (I run 4850's).



The other thing to note, with the earlier BM (6.10.58 or 6.12.32) which do get work with the 11.8 Catalyst -- they get .82 separation work units -- which process fine.

Nopem, do not, errors out running on xp 32......

ID: 53057 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Bymark
Avatar

Send message
Joined: 6 Mar 09
Posts: 51
Credit: 492,109,133
RAC: 0
Message 53058 - Posted: 10 Feb 2012, 21:45:41 UTC - in response to Message 53057.  
Last modified: 10 Feb 2012, 21:58:15 UTC

BarryAZ can lik his ass on mw if he like to do so!!!!!!!!!!

I am PUT ME MYSELF OUT from mv............
ID: 53058 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53059 - Posted: 10 Feb 2012, 21:47:07 UTC

Prices are bound to come down, so dont be too depressed, there's no way they will stay this high for good. Also another new series like 8XXX are probably 12-18 months away, that will also help depress prices of 5XXX and 6XXX both of which have full OpenCL support.

Personal guess is it becomes a real drama circa 18months from now when all have gone OpenCL (as such), but could be that future series will knock down 5XXX and 6XXX into more affordable scenarios by then. Difficult to say, but on balance I reckon it will trend that way with second prices of 5XXX and 6XXX.

Regards
Zy
ID: 53059 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile S@NL - Mellowman
Avatar

Send message
Joined: 9 Dec 07
Posts: 65
Credit: 8,015,709
RAC: 0
Message 53060 - Posted: 10 Feb 2012, 21:52:54 UTC
Last modified: 10 Feb 2012, 21:54:38 UTC

Just upgraded to BOINC 7.0.15 but it's not requesting any tasks, for any of my projects except SETI.

EDIT: I'm running dry on all projects.

Anthony.

The longer I live, the more reasons I develop for wanting to die.
ID: 53060 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Gary Roberts

Send message
Joined: 1 Mar 09
Posts: 56
Credit: 1,984,937,499
RAC: 0
Message 53062 - Posted: 10 Feb 2012, 23:09:35 UTC - in response to Message 53051.  

Those having apparent work-fetch problems with 7.X.X .... at present it works in a different way, I suspect - only that, no definitive knowledge - that its being designed to reduce cache sizes at the user end, particularly massive days long ones due to the problems that can give servers.

It certainly works in a different way but it's nothing to do with reducing cache sizes. The two cache settings now have different meanings in 7.x.x. The 'Connect Every ...' (CE) setting should now be regarded as the 'low water' mark. Many people would have this at zero (from past behaviour) and if you do, that is why BOINC wont get work until you actually run out. The 'Extra Days' (ED) setting should now be regarded as an increment to define a 'high water' mark.

So, if you want BOINC to maintain a cache between X and X.01 days, you would set CE=X and ED=0.01.

It's as simple as that. Of course, it's not really documented properly anywhere and if you gripe about that you would probably be told that nothing is guaranteed with 'bleeding edge' versions so why are you using one ... Projects will continue to try to use new features that aren't ready for prime time so you can't really blame BOINC entirely for all the teething problems. It might have been better for volunteers if the new MW 1.0x app had been released in a testing environment similar to the way that the new Einstein CL app is being tested in the Albert@Home test project. I know that requires a lot more resources at the project end but it's a lot more 'friendly' for the long suffering volunteers.

At present, the cache will reduce down without being refreshed. At the point when its almost at dry, it will then download what you set in the cache preferences all the other supply constraints being equal. Often had 200 WU downloads on other projects in one lump after apparent famine. Its feast or famine and will not play unless the cache is near zero.

This is exactly what to expect if you are using 7.x.x with 'old style' cache settings - something like CE=0 and ED=3.0 for example.


Cheers,
Gary.
ID: 53062 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 1 Sep 08
Posts: 520
Credit: 302,524,931
RAC: 15
Message 53063 - Posted: 10 Feb 2012, 23:20:26 UTC - in response to Message 53059.  

Could be -- I've over a dozen 4850 systems in play -- then again, it might encourage me to simply shut down a batch of systems and reduce the electric bill. I tend to do that in the summer anyway.


Prices are bound to come down, so dont be too depressed, there's no way they will stay this high for good. Also another new series like 8XXX are probably 12-18 months away, that will also help depress prices of 5XXX and 6XXX both of which have full OpenCL support.

Personal guess is it becomes a real drama circa 18months from now when all have gone OpenCL (as such), but could be that future series will knock down 5XXX and 6XXX into more affordable scenarios by then. Difficult to say, but on balance I reckon it will trend that way with second prices of 5XXX and 6XXX.

Regards
Zy


ID: 53063 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 1 Sep 08
Posts: 520
Credit: 302,524,931
RAC: 15
Message 53064 - Posted: 10 Feb 2012, 23:22:57 UTC - in response to Message 53062.  

Yes I figured that out a while ago -- though I think it is not quite so much 'as simple as that' -- there are (as it always the case) some other variables in play.




It's as simple as that. Of course, it's not really documented properly anywhere and if you gripe about that you would probably be told that nothing is guaranteed with 'bleeding edge' versions so why are you using one ... Projects will continue to try to use new features that aren't ready for prime time so you can't really blame BOINC entirely for all the teething problems. It might have been better for volunteers if the new MW 1.0x app had been released in a testing environment similar to the way that the new Einstein CL app is being tested in the Albert@Home test project. I know that requires a lot more resources at the project end but it's a lot more 'friendly' for the long suffering volunteers.


ID: 53064 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
nanoprobe
Avatar

Send message
Joined: 27 Jan 12
Posts: 38
Credit: 18,084,778
RAC: 0
Message 53065 - Posted: 10 Feb 2012, 23:26:20 UTC


This is exactly what to expect if you are using 7.x.x with 'old style' cache settings - something like CE=0 and ED=3.0 for example.

The new cache settings in BOINC 7.0.xx are a real PITA but if you set connect everyday to 1.00 and additional cache to 0.50 you should get work.
XP 32 and WIN7 64 both crunching away. It's the connect everyday setting that is the most important with the newer versions.


ID: 53065 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
aad

Send message
Joined: 30 Mar 09
Posts: 63
Credit: 621,582,726
RAC: 4
Message 53066 - Posted: 10 Feb 2012, 23:40:33 UTC

New 1.02 running fine on my HD6970 with Win7 64 catalyst 12.1 (preview) and BM 6.10.60
All wu's running under 4 seconds of CPU time.
GPU time average 60 seconds/wu
I use Efmer priority to keep it on 'high'.
ID: 53066 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Lennart Blume

Send message
Joined: 20 Jul 09
Posts: 4
Credit: 53,593,748
RAC: 0
Message 53067 - Posted: 11 Feb 2012, 0:19:42 UTC - in response to Message 53018.  


So I first try to go back to V0.82 by app_info.


Done that. All works fine.
I'm back and crunching.
Please keep it alive.
ID: 53067 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile S@NL - Mellowman
Avatar

Send message
Joined: 9 Dec 07
Posts: 65
Credit: 8,015,709
RAC: 0
Message 53069 - Posted: 11 Feb 2012, 0:53:25 UTC
Last modified: 11 Feb 2012, 0:54:37 UTC

I too have gotten work from MW and from SETI, but not from GPUGrid. Normally I have 2 WU's on my system (per GPU), but now I only have one crunching and it won't request a new one. I'm running BOINC 7.0.15. I'm running GPUGrid on 1 GPU.

I know this is the MW forum but maybe there's someone who could help. I also posted this on the GPUGrid forum, but I don't know how long it will take them to response, and this thread here is going like a train.

Anthony.

The longer I live, the more reasons I develop for wanting to die.
ID: 53069 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
TJ

Send message
Joined: 12 Aug 09
Posts: 262
Credit: 92,631,041
RAC: 0
Message 53070 - Posted: 11 Feb 2012, 1:22:35 UTC

Hello,
I am not getting new work, this is the driver:
2/11/2012 1:09:02 AM ATI GPU 0: ATI Radeon HD5800 series (Cypress) (CAL version 1.4.1332, 1024MB, 2720 GFLOPS peak)
That should work though?
Where can I find new CAL drivers?

Thanks.
Greetings from,
TJ
ID: 53070 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Maac59
Avatar

Send message
Joined: 27 Oct 10
Posts: 4
Credit: 9,318,199
RAC: 0
Message 53071 - Posted: 11 Feb 2012, 1:44:44 UTC

TJ:
Look at the lines following this part - they should show something like this:
2012-02-10 07:22:48 | | ATI GPU 0: ATI Radeon HD 5800 series (Cypress) (CAL version 1.4.1683, 1024MB, 991MB available, 3584 GFLOPS peak)
2012-02-10 07:22:48 | | OpenCL: ATI GPU 0: Cypress (driver version CAL 1.4.1683 (VM), device version OpenCL 1.1 AMD-APP (873.1), 1024MB)
2012-02-10 07:22:48 | | ATI GPU is OpenCL-capable

You need OpenCL to run MW on a 5800, unless you use some of the hacks described above...
Me: Go forth, GPU, plumb the depths of the galactic void to forever advance MilkyWay's lofty endeavour!
GPU: Last thing I need is more hot air...
Me: Shed the light of knowledge! Engage on the starry ways!
GPU: Warp core collapse in 10 seconds...
ID: 53071 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
TJ

Send message
Joined: 12 Aug 09
Posts: 262
Credit: 92,631,041
RAC: 0
Message 53072 - Posted: 11 Feb 2012, 1:56:03 UTC - in response to Message 53071.  

Hi Maac59,
Thanks for your quick response. I don't see any of those messages.
I know that I was crunching happily last week with MW, and now nothing works on the 2 ATI cards.
I got this message all the time:
2/11/2012 1:11:12 AM Milkyway@Home Message from server: Catalyst driver version is not OK for OpenCL application with this GPU

Where can I find the OpenCL?
Thanks.
Greetings from,
TJ
ID: 53072 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile arkayn
Avatar

Send message
Joined: 14 Feb 09
Posts: 999
Credit: 74,932,619
RAC: 0
Message 53073 - Posted: 11 Feb 2012, 2:08:43 UTC - in response to Message 53072.  

Hi Maac59,
Thanks for your quick response. I don't see any of those messages.
I know that I was crunching happily last week with MW, and now nothing works on the 2 ATI cards.
I got this message all the time:
2/11/2012 1:11:12 AM Milkyway@Home Message from server: Catalyst driver version is not OK for OpenCL application with this GPU

Where can I find the OpenCL?
Thanks.


http://support.amd.com/us/Pages/AMDSupportHub.aspx
ID: 53073 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Maac59
Avatar

Send message
Joined: 27 Oct 10
Posts: 4
Credit: 9,318,199
RAC: 0
Message 53074 - Posted: 11 Feb 2012, 2:12:54 UTC

You probably need to update your Catalyst drivers to get the latest OpenCL package. As for the solutions I was referring to, they deal with using the app_info file in convincing MW to keep using the old CAL application. Do a search on app_info on this page.
ID: 53074 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Maac59
Avatar

Send message
Joined: 27 Oct 10
Posts: 4
Credit: 9,318,199
RAC: 0
Message 53075 - Posted: 11 Feb 2012, 2:13:02 UTC
Last modified: 11 Feb 2012, 2:14:14 UTC

Deleted
ID: 53075 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 · Next

Message boards : News : Separation updated to 1.00

©2024 Astroinformatics Group