Message boards :
Graphics cards (GPUs) :
CUDA Optimised Boinc package for GPUGrid?
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 13 Mar 09 Posts: 59 Credit: 324,366 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]()
|
I saw this post where SETI users are using an optimised Boinc package with a customised app_info.xml file to override the website settings. How difficult would it be to emulate this package to work with GPU Grid or start from scratch? Rob |
Paul D. BuckSend message Joined: 9 Jun 08 Posts: 1050 Credit: 37,321,185 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I saw this post where SETI users are using an optimised Boinc package with a customised app_info.xml file to override the website settings. What is going on at SaH is not applicable to GPU Grid. They are using a series of customizations and information files to attempt to use privately created applications to run against work issued by the project. To get those packages to work and to "tune" the operation for various configurations they use these tools. Here you have an application that is controlled and issued by the project and if you run 6.5.0 or later you need no customization files at all. Having tried most of the versions my suggestion is that you use either 6.5.0 or 6.6.23 as you base BOINC version, either of which seems to work reasonably well. *BOTH* have work fetch issues of a minor nature that likely will not bother you in the slightest if you are not running on a multi-GPU system with high task throughput and lots of projects (say 10 or more). That said, these issues seem to be minor and should I ever get the developers to get their thumb out maybe they will look at them and resolve the issues. |
©2025 Universitat Pompeu Fabra