Welcome to MilkyWay@home

Coprocessor info in xml stats

Message boards : Number crunching : Coprocessor info in xml stats
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Bok

Send message
Joined: 29 Aug 07
Posts: 12
Credit: 3,164,814
RAC: 0
Message 14044 - Posted: 5 Mar 2009, 21:13:32 UTC

Are you planning on offering the coproc information in the xml stats at all ?

Seti implemented a server-side change in the code to do this and gpugrid followed..

Allows the stats sites to display the information on the host pages like here

Bok
ID: 14044 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
jedirock
Avatar

Send message
Joined: 8 Nov 08
Posts: 178
Credit: 6,140,854
RAC: 0
Message 14048 - Posted: 5 Mar 2009, 23:03:33 UTC - in response to Message 14044.  

Are you planning on offering the coproc information in the xml stats at all ?

Seti implemented a server-side change in the code to do this and gpugrid followed..

Allows the stats sites to display the information on the host pages like here

Bok

Probably not yet, as the GPU application is still technically a pre-alpha, and is not an official application.
ID: 14048 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile caferace
Avatar

Send message
Joined: 4 Aug 08
Posts: 46
Credit: 8,255,900
RAC: 0
Message 14072 - Posted: 6 Mar 2009, 4:21:26 UTC - in response to Message 14048.  

Probably not yet, as the GPU application is still technically a pre-alpha, and is not an official application.

If it's something simple on the back-end it should be done, as it gives the results more legitimacy. A slow processor can't have some of the RAC's showing unless something is going on, like GPU work. Having the coproc info in there makes some sense of things.

I imagine Bok isn't asking out of idle curiosity. He has a small stats site he runs in his free time. :D

-jim
ID: 14072 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Bok

Send message
Joined: 29 Aug 07
Posts: 12
Credit: 3,164,814
RAC: 0
Message 14119 - Posted: 6 Mar 2009, 13:06:59 UTC

Hi Jim!

it would be nothing more than upgrading to the latest server software. Which gives other nice things too, so should be done, but would require some time which I know everyone is short of...

Actually thinking about it though, I'm not sure they can implement yet as it will rely on the boinc client recognizing the ATI cards and according to the dev lists, David Anderson is waiting on ATI to send him a card in order to implement this much the same way they do the nvidia ones..

Bok :)
ID: 14119 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
SATAN
Avatar

Send message
Joined: 27 Feb 09
Posts: 45
Credit: 305,963
RAC: 0
Message 14120 - Posted: 6 Mar 2009, 13:19:37 UTC

DA and ATi have been pussyfooting around for over a year regarding ATi support. After the debacle that was the Seti release of Cuda, I think it will be a long time before ATi cards are officially supported for Boinc. Going on the rate of development at the minute, I reckon it wil be at least 12 months away.

The first anyone will know about it will be when Seti gets support, as DA and the Boinc development team seem to use Seti as their testing play pen at the minute.
Mars rules this confectionery war!
ID: 14120 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jord
Avatar

Send message
Joined: 30 Aug 07
Posts: 125
Credit: 207,206
RAC: 0
Message 14131 - Posted: 6 Mar 2009, 14:58:21 UTC - in response to Message 14120.  

...I think it will be a long time before ATi cards are officially supported for Boinc. Going on the rate of development at the minute, I reckon it wil be at least 12 months away.

Think more in the direction of 3 months. It'll be added to Boinc 6.8
It's not so difficult to add ATI support. All David is waiting for is a suitable ATI card, which he'll get from AMD/ATI. Whether it'll be CAL or OpenCL will be decided upon then.

CUDA is now working so stable that the Seti community has taken over its further development (and modification). The development of BOINC at this moment and prior to adding ATI support is to add a fully working GPU scheduler and work fetch that works together with the CPU scheduler and work fetch.

Seti could have used an ATI card about a year ago, but at that time the memory on the actual cards wasn't big enough to use reliably. At that time, the biggest cards had 128MB at a reasonably slow speed, not very useful.

Next time you think you know what you're talking about, just do some research first, if need be ask the developers you're burning down. But since burning them down to the ground seems easier to do, I suppose you'll continue with that attitude.
Jord.

The BOINC FAQ Service.
ID: 14131 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
SATAN
Avatar

Send message
Joined: 27 Feb 09
Posts: 45
Credit: 305,963
RAC: 0
Message 14134 - Posted: 6 Mar 2009, 16:18:27 UTC - in response to Message 14131.  

Seti could have used an ATI card about a year ago, but at that time the memory on the actual cards wasn't big enough to use reliably. At that time, the biggest cards had 128MB at a reasonably slow speed, not very useful.


Please don't tell me to go and do research when you haven't even got this fact correct. The Mac Pro from January last year shipped with the HD2600 XT which was already 6 months old at that point, this had 256MB. So I am sorry Sir but you are incorrect.

As for my opinions regarding DA and Boinc development, they are just that, my personal opinions, gathered from 2.5 years of crunching Seti on Windows and Mac OSX. Lets leave any arguements out of here. Enough mud has been slung over at Seti regarding, DA, Cuda, etc, lets not sling anymore.
Mars rules this confectionery war!
ID: 14134 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Misfit
Avatar

Send message
Joined: 27 Aug 07
Posts: 915
Credit: 1,503,319
RAC: 0
Message 14199 - Posted: 7 Mar 2009, 0:51:49 UTC - in response to Message 14131.  

Seti could have used an ATI card about a year ago, but at that time the memory on the actual cards wasn't big enough to use reliably. At that time, the biggest cards had 128MB at a reasonably slow speed, not very useful.

EEENT Wrong! I had a Radeon X850 XT PE four years ago. It had 256MB.

Next time you think you know what you're talking about, just do some research first, if need be ask the developers you're burning down. But since burning them down to the ground seems easier to do, I suppose you'll continue with that attitude.

Practice what you preach, Jordless.
me@rescam.org
ID: 14199 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Paul D. Buck

Send message
Joined: 12 Apr 08
Posts: 621
Credit: 161,934,067
RAC: 0
Message 14217 - Posted: 7 Mar 2009, 7:39:57 UTC - in response to Message 14131.  

Next time you think you know what you're talking about, just do some research first, if need be ask the developers you're burning down. But since burning them down to the ground seems easier to do, I suppose you'll continue with that attitude.

Yes, but you presuppose that they don't deserve to be burned, to the ground or some other altitude.

Most of their problems, including reputation are self-created.
ID: 14217 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile speedimic
Avatar

Send message
Joined: 22 Feb 08
Posts: 260
Credit: 57,387,048
RAC: 0
Message 14245 - Posted: 7 Mar 2009, 14:53:17 UTC - in response to Message 14044.  

Are you planning on offering the coproc information in the xml stats at all ?

Seti implemented a server-side change in the code to do this and gpugrid followed..

Allows the stats sites to display the information on the host pages like here

Bok


...or have separate stats for GPU like suggested here: Separated stats for CPUs and GPUs.

mic.


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

Message boards : Number crunching : Coprocessor info in xml stats

©2024 Astroinformatics Group