Will BOINC utilize both GPU's in a...

Questions and Answers : Windows : Will BOINC utilize both GPU's in a...
Message board moderation

To post messages, you must log in.

1 · 2 · 3 · Next

AuthorMessage
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1112553 - Posted: 3 Jun 2011, 3:08:46 UTC

Will BOINC utilize both GPU's in a CrossFire setup and for arguments sake two GPU's in a dual GPU card ?
ID: 1112553 · Report as offensive
Profile Fred J. Verster
Volunteer tester
Avatar

Send message
Joined: 21 Apr 04
Posts: 3252
Credit: 31,903,643
RAC: 0
Netherlands
Message 1112618 - Posted: 3 Jun 2011, 11:14:55 UTC - in response to Message 1112553.  

Will BOINC utilize both GPU's in a CrossFire setup and for arguments sake two GPU's in a dual GPU card ?


Yes, sometimes you'll need a cc_config.xml file to make BOINC aware of the
GPUs in the system.

Cc_config.xml .

And you can use the LUNATICs Installer V0.37, if you use nVIDIA (FERMI) cards.


ID: 1112618 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1112636 - Posted: 3 Jun 2011, 12:51:54 UTC - in response to Message 1112618.  

The config files only needed for the ATI's right since I think the nVIDIAS are by default accepted / used by BOINC.
ID: 1112636 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1112643 - Posted: 3 Jun 2011, 13:16:09 UTC - in response to Message 1112636.  

The config files only needed for the ATI's right since I think the nVIDIAS are by default accepted / used by BOINC.


Nope. Two different files you're talking about.

The CC_Config.XML file is required for any dual-GPU setup, regardless if it is nVidia or ATi.

App_Info.XML is required for ATi GPUs since there's no official app, the App_Info.XML file tells BOINC to use a local app instead of one sent by the server.
ID: 1112643 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1112887 - Posted: 4 Jun 2011, 4:36:52 UTC - in response to Message 1112643.  

Thx, then I'll have to have a look at both files since ATM the cards I got my eye on for a new build are CrossFireX ATI's.
ID: 1112887 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1113756 - Posted: 6 Jun 2011, 6:41:25 UTC - in response to Message 1112643.  

App_Info.XML is required for ATi GPUs since there's no official app, the App_Info.XML file tells BOINC to use a local app instead of one sent by the server.


I was doin a bit of thinking on this but why hasnt an official app been release by now if people can simply use an App_Info file ? Would it really be that hard for the powers that be to get something implemented for ATI ?
ID: 1113756 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1113759 - Posted: 6 Jun 2011, 6:58:56 UTC - in response to Message 1113756.  
Last modified: 6 Jun 2011, 6:59:15 UTC

What you see as "simply an app_info.xml file" has cost the Lunatics developers (3rd party devs) lots of months to test, rerun, perfect and test some more. If that would've been done by Seti, it would've cost them lots of money that they can better spend elsewhere. Hence them applauding the users using the anonymous platform.

At least with the anonymous platform the applications can be ported to and compiled for a lot of (be it obscure) platforms and OSes that the project developers have never heard of or thought to port to.

Now, while the ATI app may work under anonymous platform, it's a whole different kettle of fish just transposing it back as the main app, as that would also cost a lot of testing and checking if it worked all right. Especially so since there are extra lines in the app_info.xml file through which you tell how the app should be used, which may not be that easy to use in the normal platforms. Anyway, again it'll cost money that the project admin would like to spend elsewhere.

And since the app_info.xml works... why bother?
ID: 1113759 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1113791 - Posted: 6 Jun 2011, 8:52:35 UTC - in response to Message 1113759.  
Last modified: 6 Jun 2011, 9:04:53 UTC

And since the app_info.xml works... why bother?
Fair enough...

As for properly setting up the app_info & CC_config files, I wouldnt know where to begin without F'in anything up. When it comes to PHP, XML I'm a total noob that almost always unintentionally messes something up no matter how well intended my attempts.

I'm sure there's a question in there somewhere but I wana take a second look at the code before I start actually askin for help which I'll probably end up doin.

On a similar note, how often would these two files need updating or is it like the Ronco Compact Rotisserie & BBQ Oven, just set it and forget it ?

Edit: Looks like I wont even have to worry about GPU workloads anyway since the cards I want will be ATI's and then there's this.

Projects with ATI Stream (CAL)
Collatz Conjecture
DNETC@Home
Milkyway@Home **

I don't currently run any of those projects and if they're the only ones that have ATI GPU workloads then I should be good to go with nothing to worry about since all I would technically be doing are CPU WU's.
ID: 1113791 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1113839 - Posted: 6 Jun 2011, 12:04:14 UTC - in response to Message 1113791.  

On a similar note, how often would these two files need updating or is it like the Ronco Compact Rotisserie & BBQ Oven, just set it and forget it ?


It's more like a "set-it-and-check-for-updates" kinda thing. Once you use an App_info.XML file, you are essentially telling the servers, "Don't worry about sending me automatic science application updates, I have an unsupported application and I am responsible for making sure it is current".

Edit: Looks like I wont even have to worry about GPU workloads anyway since the cards I want will be ATI's and then there's this.

Projects with ATI Stream (CAL)
Collatz Conjecture
DNETC@Home
Milkyway@Home **

I don't currently run any of those projects and if they're the only ones that have ATI GPU workloads then I should be good to go with nothing to worry about since all I would technically be doing are CPU WU's.


Those are all projects that have official ATi applications. Projects only list what they officially support.

The App_Info.XML file allows third-party developers to write unsupported applications for otherwise unsupported hardware. Because the software is written by a third-party, it is the user's responsibility to check for updates on a regular basis to ensure that no significant changes have occurred to the science app and validation process.
ID: 1113839 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1113869 - Posted: 6 Jun 2011, 13:52:47 UTC - in response to Message 1113791.  

As for properly setting up the app_info & CC_config files, I wouldnt know where to begin without F'in anything up. When it comes to PHP, XML I'm a total noob that almost always unintentionally messes something up no matter how well intended my attempts.

You can always ask for help, if you're not sure. Best do that in the Number Crunching forum as the people who live and breathe that stuff live there.

Read through the Optimized applications and other Binaries thread for which app you require. I'd think the one in Message 1071730.

As for both app_info.xml and cc_config.xml files, the XML used in these isn't true XML. It's pseudo XML specially developed for BOINC.

For the anonymous platform, see for options here in the User Wiki; see for options in the cc-config.xml file, the client configuration file.

Read through it all first. Ask questions. You can ask them here, we'll answer them as far as our knowledge goes.
ID: 1113869 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1113913 - Posted: 6 Jun 2011, 15:17:05 UTC - in response to Message 1113839.  

On a similar note, how often would these two files need updating or is it like the Ronco Compact Rotisserie & BBQ Oven, just set it and forget it ?


It's more like a "set-it-and-check-for-updates" kinda thing. Once you use an App_info.XML file, you are essentially telling the servers, "Don't worry about sending me automatic science application updates, I have an unsupported application and I am responsible for making sure it is current".
Check where for updates, and I'm assuming you mean for both files or just the App_info one ?

Or do you just mean making sure I always have the latest BOINC client in which case the files would be set n forget.


ID: 1113913 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1113919 - Posted: 6 Jun 2011, 15:26:33 UTC - in response to Message 1113913.  

In case of anonymous platform, you have to check regularly at the site where you got the anonymous platform file & application from. These normally travel side-by-side, meaning that when you get the 3rd party science application, it'll come with its own correct app_info.xml file.
ID: 1113919 · Report as offensive
Profile perryjay
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3377
Credit: 20,676,751
RAC: 0
United States
Message 1114039 - Posted: 6 Jun 2011, 19:38:08 UTC - in response to Message 1113913.  

You don't always need to update the BOINC manager to the latest/greatest version but the guys and gals at Lunatics are always busy testing and improving their stuff. If they release a new optimized package you won't get it automatically. You will have to get it and install it yourself. If you don't, it is possible that a new app issued by SETI won't be included in the opt_app you are running so you wont be able to run it.

The best example of that is Lunatics old V12 opt_app and the new fermi cards that just came out. It was found the V12 app caused the Fermi work to give false -9 result overflow results. The crew at Lunatics got right on this problem, found a cure and came out with the new package but we are still plagued with set and forget types that got new cards but didn't update the opt_app.


PROUD MEMBER OF Team Starfire World BOINC
ID: 1114039 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 1114083 - Posted: 6 Jun 2011, 23:14:45 UTC

In maybe a couple of weeks, Lunatics should be coming out with a new version of the installer that will include the ATI apps as well. We are Alpha testing it right now to make sure that everything is correct.

ID: 1114083 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1114269 - Posted: 7 Jun 2011, 14:24:00 UTC - in response to Message 1114083.  

I'm actually looking at building a new system for gaming / BOINC which includes dual SLI NVIDIA FERMI cards so all I should really need is maybe a CC_Config file to make sure both GPU's are seen.

I decided against the ATI's for various reasons, one of which is making sure I always had a good app_info file for all the projects I would be running.

Here's the builds wishlist on NewEgg.

http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=16250245
ID: 1114269 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 446,358
RAC: 0
Germany
Message 1114321 - Posted: 7 Jun 2011, 15:42:04 UTC - in response to Message 1114269.  

...one of which is making sure I always had a good app_info file for all the projects I would be running...

An app_info.xml file is per project. So, you'd only need one for each project that has no stock ATi application.

Gruß,
Gundolf
ID: 1114321 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1114402 - Posted: 7 Jun 2011, 23:02:43 UTC - in response to Message 1114321.  

...one of which is making sure I always had a good app_info file for all the projects I would be running...

An app_info.xml file is per project. So, you'd only need one for each project that has no stock ATi application.

Gruß,
Gundolf

I figured the per project part from what was previously said. My luck I would end up with 10+ files needing to be kept after and would forget to check for updates half the time. In any case, it seems after some more readinv nVIDIA cards in general would be better than the ATI's.
ID: 1114402 · Report as offensive
Profile perryjay
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3377
Credit: 20,676,751
RAC: 0
United States
Message 1114433 - Posted: 8 Jun 2011, 1:39:00 UTC

Just to give a little update, the new installer v0.38 has gone into beta testing and the guys and gal at Lunatics are doing everything they can to get it tested and out to the general public. Shouldn't be long at all now.


PROUD MEMBER OF Team Starfire World BOINC
ID: 1114433 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1114479 - Posted: 8 Jun 2011, 5:58:21 UTC - in response to Message 1114269.  

I'm actually looking at building a new system for gaming / BOINC which includes dual SLI NVIDIA FERMI cards so all I should really need is maybe a CC_Config file to make sure both GPU's are seen.

I decided against the ATI's for various reasons, one of which is making sure I always had a good app_info file for all the projects I would be running.

You don't need cc_config.xml to use both GPUs if they are the same type/model/version -
BOINC will use them both automatically.

With NVIDIA you don't need app_info.xml for SETI

If you are interested in other projects - I don't know which of them works "by default" on ATI only and not on NVIDIA FERMI


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1114479 · Report as offensive
Profile Andrew C. McNamara
Avatar

Send message
Joined: 1 Aug 00
Posts: 67
Credit: 0
RAC: 0
United States
Message 1114904 - Posted: 9 Jun 2011, 3:30:47 UTC - in response to Message 1114479.  

Well, with my laptop being what it is I might not run SETI much at all on it and then go full force like I use to years back after I get my new gaming system built which will include a SLI of two FERMI cards.

With everything I have been reading not only here but other sites as well it seems that I wont need to use a cc_config file since both cards will be identical nor an app_info file because both cards will be nVIDIA. So since projects that do use the GPU have a standard nVIDIA file option I should be all set with nothing to worry about when my custom build is done.
ID: 1114904 · Report as offensive
1 · 2 · 3 · Next

Questions and Answers : Windows : Will BOINC utilize both GPU's in a...


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.