Questions and Answers :
Getting started :
Compatibility with GIMPS
Message board moderation
Author | Message |
---|---|
Spinningspark Send message Joined: 5 Oct 07 Posts: 9 Credit: 43,185 RAC: 0 |
Hi, I would like to take part in SETI@Home but I am already running Prime95 on the same machine for the GIMPS project. Is there going to be any compatibility issues? In particular, Prime95 runs at the lowest possible priority so only takes machine cycles when nothing else wants them. Will the BOINC system leave anything for Prime95 to use? Thanks for helping. Spinningspark By the way, I had to jump through hoops to post this message. You have to be logged on to post, but to log on you have to register, but to register you have to download BOINC first, but I did not want to do this until I found out if BOINC will upset Prime95, but to find out I have to post a message, but . . . Something not right there. Eventually, I found out I could get round it by registering as pre 5.0 client. If that is going to cause a problem when I do download BOINC someone please tell me what to do. |
PaperDragon Send message Joined: 27 Aug 99 Posts: 170 Credit: 8,903,782 RAC: 4 |
Likely this question should be posted on the BOINC Message boards. That way you do not have to mess around with signing up for a project. Now as for your question, It might depend if GIMPS is slightly, the same, of lower prioity then BOINC. If I rember correctly, there are different degrees of low prioity. If it is the same then BOINC will complete for CPU cycles and take longer to complete work units; the same for GIMPS - longer completeion times. If either is slightly higher, then it might start to hog the CPU from the other. SL |
Spinningspark Send message Joined: 5 Oct 07 Posts: 9 Credit: 43,185 RAC: 0 |
You think I should just try it and see? Would it be messing your project around if I took some WUs and then cancelled after trying? |
PaperDragon Send message Joined: 27 Aug 99 Posts: 170 Credit: 8,903,782 RAC: 4 |
You can give it ago. BOINC is set up to handle people not finishing work units. Work Units have a deadline. They just get re-issued if not returned, or error out. If you decided to leave SETI, just abort the work units so that they can be re-issued faster. SL |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
The different DC projects do not play well with each othet because they tend to run at slightly different priorities. There are a couple of possibilities. Run one for a half a day and the other for the other half of the day (use a script fired by a time to turn one off and the other on - details differ by OS). If you have multiple CPUs, restrict each DC project to half of the CPUs. BOINC WIKI |
Spinningspark Send message Joined: 5 Oct 07 Posts: 9 Credit: 43,185 RAC: 0 |
The different DC projects do not play well with each othet because they tend to run at slightly different priorities. Just to let you know, I have been running SETI@Home alongside Prime95 for about a week now. There have not been any issues and they seem to share the CPU about 50/50 when nothing else is running. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
The different DC projects do not play well with each othet because they tend to run at slightly different priorities. That means that on that particular OS the two have exactly the same priority. BOINC WIKI |
©2024 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.