Joined: 9 Jun 99
Task Checkpoint to Disk at most every x seconds.
Note the at most in the preference text. This preference is a guideline, the project's science application does not have to follow it. In the case of Seti, it doesn't.
On my i5-2500K with that preference set to 90 seconds, it'll be about 61 seconds for the CPU Seti v7 application. Not sure how much for the GPU application, or the Astropulse applications.
It depends on the amount of the floating operations your CPU can do per second, more than it does so for actual speed. Do know that reading from disk and writing to it can slow this down, depending on speed of and congestion on the disk.
...there is no reason it should not be doable, as I gather that many people run BOINC over a network.
You gather or you think? As I haven't heard anyone yet say that they run BOINC over the network and then expect everything to be stable.
- BOINC in compatibility mode (Windows XP, SP3),
At the time I was trying anything and everything to get BOINC to stabilize. Windows XP works with less resources, so why not try it? Compatibility Mode will be one of those things that I phase out and monitor.
it would mean continual activity on that hard drive;
And that's bad, because of... what?
According to this page http://boinc.berkeley.edu/wiki/GPU_computing I should not expect to be able to do GPU processing with SAH on an ATI chipset.
Thanks for proof reading the page. It's now edited, Seti's been added. Also the fact that it can do GPU apps on Linux these days.
Next time, don't expect everything in the Wiki to be up-to-date. BilBg may have pointed out that I do a lot of the documentation, but then I seem to be the only one as well. I know that some of the Wiki is hopelessly out of date, as are my FAQs, but there is just not enough time for me to change that all in the next week. So I don't even try.
Best check http://setiathome.berkeley.edu/apps.php, which is the Seti Applications page. That one will be up-to-date at any time.
In the mean time your AuthenticAMD is leaving lost work in its tracks. It went from hostID 7107119 to hostID 7114216, leaving 54 perfectly fine tasks in its wake. These will now have to time out first, before they'll be resent to other computers. During this time they'll stay in Seti's database for nought. Just cluttering, taking up space.
Please keep an eye on this behaviour, that your host doesn't do more of this hostID skipping, as that means there's something really wrong with your set up. And it'll only irritate your wingmen who now have to wait much longer for their credit.
Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.
©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.