Unfortunately, a driver which works with one application for one developer may not work for a different developer with a different application, even on the same card.
I was recently comparing MilkyWay, where a user was getting nothing but errors with Catalyst 13.4 and their current app, but success with 13.1 That's in complete contrast with SETI, where the developer has got his app running with 13.4, but can't make 13.1 work whatever he does. I think it would be helpful for BOINC (centrally) to act as an information clearing-house for project developers, covering issues like this, even before considering the database. A listing of known working developer tools (and version numbers)? Bugs found and squashed during an upgrade cycle? References to open developer support tickets raised with specific BOINC-related issues in mind? But when you do get to the database, I agree that the coprocessor data should be in a relational table linked by HostID to the main host table: there's the continuing problem of separate and different GPUs in a single host, and scheduling when one supports double precision and the other doesn't, to cite an obvious example. >________________________________ > From: Jon Sonntag <[email protected]> >To: David Anderson <[email protected]> >Cc: "BOINC Developers Mailing List @berkeley.edu" <[email protected]> >Sent: Wednesday, 5 June 2013, 14:30 >Subject: Re: [boinc_dev] Fwd: Get OpenCL details on coprocessor line in >account->computer details > > >The SerialNum field is used to store what little information is kept about >the coprocessors which is mainly the type and driver version. The >SerialNum field also contains the BOINC client version. It doesn't contain >a serial number. Given AMD's faulty drivers of late, if would be helpful >to know exactly which GPU models work with which drivers and whether a >driver allows the GPU to complete the work faster or slower than a previous >driver. That, and no DBA with any self respect would put multiple data >fields into a single field, especially if the field name has nothing to do >with any of the data points stored in it. Maybe a coprocessor table with a >foreign key pointing back to the host table would be less obscure? It >could then be referenced in the results table so that a person could really >know which GPU make and model completed which result. > >Jon Sonntag > > >On Tue, Jun 4, 2013 at 11:18 PM, David Anderson <[email protected]>wrote: > >> Not currently; OpenCL info is not stored in the database. >> -- David >> >> On 04-Jun-2013 9:35 AM, Jorden van der Elst wrote: >> >> >>> Can we get the OpenCL details of the detected GPU(s) in project's user >>> account->computer details as well, please? Or only that line when it >>> comes to AMD/ATI GPUs? At present we're showing only the CAL line, >>> while in most project's cases we need the information in the OpenCL >>> line. If it's detected at least. Therefore also when it's not >>> detected, state that it's not detected? >>> >>> With thanks, >>> >>> -- >>> -- Jord van der Elst. >>> >>> >>> -- >>> -- Jord van der Elst. >>> ______________________________**_________________ >>> boinc_dev mailing list >>> [email protected] >>> http://lists.ssl.berkeley.edu/**mailman/listinfo/boinc_dev<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> >>> To unsubscribe, visit the above URL and >>> (near bottom of page) enter your email address. >>> >>> ______________________________**_________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/**mailman/listinfo/boinc_dev<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and >(near bottom of page) enter your email address. > > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
