GUI_RPC and GPUs

Message boards : API : GUI_RPC and GPUs
Message board moderation

To post messages, you must log in.

AuthorMessage
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 29279 - Posted: 6 Dec 2009, 12:51:44 UTC

Is it possible to retrieve information about installed GPUs via GUI_RPC?

<get_host_info> only returns CPU data. So does <get_state>.
ID: 29279 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15492
Netherlands
Message 29280 - Posted: 6 Dec 2009, 13:28:38 UTC - in response to Message 29279.  

Can't you read the sched_request*.xml file? The info about the videocard is in there as well.

In my case, for the Einstein sched_request*.xml file:

<coprocs>
<coproc_ati>
   <count>1</count>
   <name>ATI Radeon HD 3800 (RV670)</name>
   <req_secs>864.864000</req_secs>
   <req_instances>1.000000</req_instances>
   <estimated_delay>0.000000</estimated_delay>
   <target>3</target>
   <localRAM>512</localRAM>
   <uncachedRemoteRAM>256</uncachedRemoteRAM>
   <cachedRemoteRAM>64</cachedRemoteRAM>
   <engineClock>669</engineClock>
   <memoryClock>829</memoryClock>
   <wavefrontSize>64</wavefrontSize>
   <numberOfSIMD>4</numberOfSIMD>
   <doublePrecision>1</doublePrecision>
   <pitch_alignment>64</pitch_alignment>
   <surface_alignment>256</surface_alignment>
   <maxResource1DWidth>-1</maxResource1DWidth>
   <maxResource2DWidth>8192</maxResource2DWidth>
   <maxResource2DHeight>8192</maxResource2DHeight>
   <CALVersion>1.4.403</CALVersion>
    <atirt_detected/>
</coproc_ati>
    </coprocs>

ID: 29280 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 29281 - Posted: 6 Dec 2009, 13:52:04 UTC

Fred M and I are chatting with Jason about automating the flop-balancing for optimised SETI applications, while we're waiting for app_version specific TDCFs. (lunatics)

GUI_RPC would be a more 'professional' way to go than scraping sched_requests - though knowing Jason, he'll probably end up querying the hardware directly. Having it in the GUI - I think leaving it out is just an oversight - would also expose it to remote managers like BoincTasks.
ID: 29281 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15492
Netherlands
Message 29282 - Posted: 6 Dec 2009, 14:02:00 UTC - in response to Message 29281.  

But you only have to read it once. I don't expect my videocard/GPU to change every so many seconds, do you? So you'd only have to read it at app-start.
ID: 29282 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 29283 - Posted: 6 Dec 2009, 14:27:24 UTC - in response to Message 29282.  

But you only have to read it once. I don't expect my videocard/GPU to change every so many seconds, do you? So you'd only have to read it at app-start.

I don't expect my CPU to change every few seconds, either.

It just seems inconsistent to restrict get_host_info to CPU only in this day and age. It shouldn't be any more difficult to spit out the <coprocs> vector in response to a GUI_RPC, than it is when preparing a sched_request.
ID: 29283 · Report as offensive

Message boards : API : GUI_RPC and GPUs

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.