Message boards :
Questions and problems :
SETI@HOME and GUP and CPU units
Message board moderation
Author | Message |
---|---|
Send message Joined: 29 Nov 17 Posts: 1 |
Is there a way to tell BOINC to download only GPU data packets..I was looking at all tasks and there were no GPU packets scheduled only CPU packets which will take a a few weeks or more to work through. Normally I see more GPU packets downloaded than CPU only packets. |
Send message Joined: 25 May 09 Posts: 1283 |
A very specific SETI@Home question - why not ask on the project's own Q&A or number crunching forum? |
Send message Joined: 29 Aug 05 Posts: 15477 |
Your account -> project preferences -> edit preferences -> uncheck "Use CPU" -> save preferences. In the case of Seti, that's here: https://setiathome.berkeley.edu/prefs.php?subset=project Any work still in cache for the CPU will run its course, but new work for the CPU will not be asked for. |
Send message Joined: 15 Dec 17 Posts: 2 |
request for larger data 'chunks' although new to the forum, I have been running SETI<at> home for a couple of years. I now run the program on a newer, 64 bit computer with a four-core processor, running seti as a background 'task'. I am getting well in advance on the deadline dates for processing ( so far, the deadline of pending work is February 2018!) I was wondering, is there a option to enable larger segments of data downloads for larger capacity computers, that would reduce the lead times? the way things are going, I will have 2019 deadlines by may of next year ! |
Send message Joined: 25 May 09 Posts: 1283 |
The size of data is very much a project decision. The size of SETI tasks is set so that they run in a sensible time on everything from the fastest gpu to the slowest android device. Likewise dead lines are set to give everyone a fair chance, and so faster machines will get through comfortably within the 6 to 8 weeks allowed. Baskcally if you are returning your work within the deadline don't worry as you will get the credit due. |
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.