BOINC 5.8 now ready for public release.

Author	Message
Captain Avatar Volunteer tester Send message Joined: 17 May 99 Posts: 15133 Credit: 529,088 RAC: 0	Message 511765 - Posted: 1 Feb 2007, 20:58:47 UTC BOINC 5.8 now ready for public release. Some of the highlights for this release include: * Simple GUI (Complements of World Community Grid) * Basic CPU identification * CPU throttling * New CPU scheduler * New work fetch policy * Improved memory management Updated on my Pent D with no problems, I do like the simple view very user friendly. http://boinc.berkeley.edu/download.php ID: 511765 ·

JAMC Volunteer tester Send message Joined: 2 Jan 07 Posts: 71 Credit: 9,521,522 RAC: 0	Message 511798 - Posted: 1 Feb 2007, 22:25:30 UTC Can you install over the old version or do you need to uninstall then install the new version? Thanks! ID: 511798 ·

[B^S] madmac Volunteer tester Send message Joined: 9 Feb 04 Posts: 1175 Credit: 4,754,897 RAC: 0	Message 511807 - Posted: 1 Feb 2007, 22:32:32 UTC Is there an optimised version? ID: 511807 ·

CJOrtega Send message Joined: 15 May 99 Posts: 186 Credit: 1,126,273 RAC: 0	Message 511816 - Posted: 1 Feb 2007, 22:43:27 UTC - in response to Message 511798. Can you install over the old version or do you need to uninstall then install the new version? Thanks! WinXp Home, installed, as a service, over version 5.4.11, on 3 systems. No problem. Just stop the Boinc service and install. ID: 511816 ·

n7rfa Volunteer tester Send message Joined: 13 Apr 04 Posts: 370 Credit: 9,058,599 RAC: 0	Message 511845 - Posted: 1 Feb 2007, 23:32:19 UTC I see that Linux is still limited to 5.4.11. Any idea when the new version will be available for Linux? ID: 511845 ·

htrae Volunteer tester Send message Joined: 3 Apr 99 Posts: 241 Credit: 768,379 RAC: 0	Message 511848 - Posted: 1 Feb 2007, 23:37:35 UTC Last modified: 1 Feb 2007, 23:39:01 UTC Boinc 5.8.8 installed over top of Crunch3r 5.5.0 with no problems so far. Installed as single user without auto start on log-in...Windows XP Home SP2. ID: 511848 ·

EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0	Message 511852 - Posted: 1 Feb 2007, 23:43:40 UTC Last modified: 1 Feb 2007, 23:49:11 UTC Just installed 5.8.8 and I found one issue - the host venue is set to be "none". "...location: (none); project prefs: default" update: did a manual update (using boincview) and the venue is now correct. ID: 511852 ·

htrae Volunteer tester Send message Joined: 3 Apr 99 Posts: 241 Credit: 768,379 RAC: 0	Message 511855 - Posted: 1 Feb 2007, 23:48:45 UTC - in response to Message 511852. Just installed 5.8.8 and I found one issue - the host venue is set to be "none". "...location: (none); project prefs: default" Hit Update. ID: 511855 ·

Anthony Apfelbeck Send message Joined: 26 May 06 Posts: 72 Credit: 17,425,405 RAC: 31	Message 511861 - Posted: 1 Feb 2007, 23:57:01 UTC The install worked fine for me. By the way, what is different about these two items in the new version? * New work fetch policy * Improved memory management Join the Fire Service Team ID: 511861 ·

W-K 666 Volunteer tester Send message Joined: 18 May 99 Posts: 19730 Credit: 40,757,560 RAC: 67	Message 511904 - Posted: 2 Feb 2007, 1:01:49 UTC - in response to Message 511807. Is there an optimised version? Why? ID: 511904 ·

Pooh Bear 27 Volunteer tester Send message Joined: 14 Jul 03 Posts: 3224 Credit: 4,603,826 RAC: 0	Message 511909 - Posted: 2 Feb 2007, 1:07:14 UTC The CLIENT is upgraded to 5.8.8 the SETI applications are still the same, currently. The client does no computing, so optimizing doesn't really give you anything. I installed on all my systems. Love it. Benchmarking seemed faster. My movie https://vimeo.com/manage/videos/502242 ID: 511909 ·

John McLeod VII Volunteer developer Volunteer tester Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0	Message 511961 - Posted: 2 Feb 2007, 3:29:58 UTC - in response to Message 511861. The install worked fine for me. By the way, what is different about these two items in the new version? * New work fetch policy * Improved memory management First the memory management. You can set the maximum fraction of RAM that the tasks can use in total for both the times you are using the keyboard and mouse as well as the times that you are not using those. Reducing RAM usage when you are active can improve the responsiveness of the computer. Second for the work fetch policy. 5.4.11 and earlier kept "connect every X days", or min_queue, work for each project that was attached with a couple of exceptions. 5.8.8 divides min_queue among the projects that are reachable so that the host has a bit more than min_queue work on hand. 5.4.11 would not fetch any work if there was a task that was in deadline trouble. 5.8.8 will always attempt to keep min_queue work on the host with the exception of the case where all projects that are attached have a task that is in deadline trouble. The CPU scheduler is also changed. 5.4.11 would enter a strict Earliest Deadline First mode when any task on the system was in deadline trouble. In this mode all of the CPUs would be working on the earliest deadline tasks. 5.8 does this differently. If a task is in deadline trouble, then the task with the earliest deadline from that project is started. There may be other tasks from other projects that do not have deadline trouble - these tasks are ignored for EDF for the moment. Also, if the host has multiple CPUs, it is possible for one to be running a task in EDF, and have another running a task picked by Highest Short Term Debt First. The determination of when a task is in deadline trouble has also changed. In 5.4.11 if any of the following failed the task was in deadline trouble. If the deadline is less than 24 hours in the future, if the deadline is less than 2* min_queue in the future, if the task will not complete by round robin simulation in < 90% of the time to the deadline. This has been replaced. 5.8 uses only one criteria. If the task will not complete by round robin simulation in < 90% of the time to the computation deadline it is in deadline trouble. The computation deadline is the report deadline - (min_queue + project switch interval + 1 day). BOINC WIKI ID: 511961 ·

[B^S] madmac Volunteer tester Send message Joined: 9 Feb 04 Posts: 1175 Credit: 4,754,897 RAC: 0	Message 512085 - Posted: 2 Feb 2007, 10:01:35 UTC Ok just done 5.8, I have a few problems with climate. It is looking for the Sulphur models and there is none. Kept on getting this message; 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_data_4.22_windows_intelx86.zip not found 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_um_4.22_windows_intelx86.zip not found 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_se_4.22_windows_intelx86.zip not found It has downloaded my hadcm models, but keep on getting cannot download sulphur etc every minute. What should I do? ID: 512085 ·

Grant (SSSF) Volunteer tester Send message Joined: 19 Aug 99 Posts: 13961 Credit: 208,696,464 RAC: 304	Message 512093 - Posted: 2 Feb 2007, 11:04:55 UTC - in response to Message 511845. I see that Linux is still limited to 5.4.11. Any idea when the new version will be available for Linux? They've still got a couple of bugs to sort out in the LINUX version. Grant Darwin NT ID: 512093 ·

Pooh Bear 27 Volunteer tester Send message Joined: 14 Jul 03 Posts: 3224 Credit: 4,603,826 RAC: 0	Message 512095 - Posted: 2 Feb 2007, 11:09:50 UTC - in response to Message 512085. Ok just done 5.8, I have a few problems with climate. It is looking for the Sulphur models and there is none. Kept on getting this message; 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_data_4.22_windows_intelx86.zip not found 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_um_4.22_windows_intelx86.zip not found 02/02/2007 09:51:40\|\|file projects/climateprediction.net/sulphur_se_4.22_windows_intelx86.zip not found It has downloaded my hadcm models, but keep on getting cannot download sulphur etc every minute. What should I do? Abort the transfers. That is a bug on CPDN side, not BOINC side. My movie https://vimeo.com/manage/videos/502242 ID: 512095 ·

[B^S] madmac Volunteer tester Send message Joined: 9 Feb 04 Posts: 1175 Credit: 4,754,897 RAC: 0	Message 512096 - Posted: 2 Feb 2007, 11:10:37 UTC Thank you, thought so I have done it. ID: 512096 ·

Anthony Apfelbeck Send message Joined: 26 May 06 Posts: 72 Credit: 17,425,405 RAC: 31	Message 512106 - Posted: 2 Feb 2007, 11:23:00 UTC - in response to Message 511961. The install worked fine for me. By the way, what is different about these two items in the new version? * New work fetch policy * Improved memory management First the memory management. You can set the maximum fraction of RAM that the tasks can use in total for both the times you are using the keyboard and mouse as well as the times that you are not using those. Reducing RAM usage when you are active can improve the responsiveness of the computer. Second for the work fetch policy. 5.4.11 and earlier kept "connect every X days", or min_queue, work for each project that was attached with a couple of exceptions. 5.8.8 divides min_queue among the projects that are reachable so that the host has a bit more than min_queue work on hand. 5.4.11 would not fetch any work if there was a task that was in deadline trouble. 5.8.8 will always attempt to keep min_queue work on the host with the exception of the case where all projects that are attached have a task that is in deadline trouble. The CPU scheduler is also changed. 5.4.11 would enter a strict Earliest Deadline First mode when any task on the system was in deadline trouble. In this mode all of the CPUs would be working on the earliest deadline tasks. 5.8 does this differently. If a task is in deadline trouble, then the task with the earliest deadline from that project is started. There may be other tasks from other projects that do not have deadline trouble - these tasks are ignored for EDF for the moment. Also, if the host has multiple CPUs, it is possible for one to be running a task in EDF, and have another running a task picked by Highest Short Term Debt First. The determination of when a task is in deadline trouble has also changed. In 5.4.11 if any of the following failed the task was in deadline trouble. If the deadline is less than 24 hours in the future, if the deadline is less than 2* min_queue in the future, if the task will not complete by round robin simulation in < 90% of the time to the deadline. This has been replaced. 5.8 uses only one criteria. If the task will not complete by round robin simulation in < 90% of the time to the computation deadline it is in deadline trouble. The computation deadline is the report deadline - (min_queue + project switch interval + 1 day). Great information. Thanks! Join the Fire Service Team ID: 512106 ·

SATAN Send message Joined: 27 Aug 06 Posts: 835 Credit: 2,129,006 RAC: 0	Message 512168 - Posted: 2 Feb 2007, 15:50:22 UTC Just installed 5.8.8 on both XP Laptop and Mac desktop, already showing a 10% increase in crunching speed, this is on top of using optimized apps on both OS. Has anyone else noticed a speed bump? ID: 512168 ·

Svenie25 Volunteer tester Send message Joined: 20 Feb 05 Posts: 29 Credit: 297,165 RAC: 0	Message 512183 - Posted: 2 Feb 2007, 16:19:23 UTC Last modified: 2 Feb 2007, 16:33:23 UTC On my C2D E6300 with Win XP Prof, iÃ‚Â´ve got a problem with 5.8.8. The estimated prcessor-time is growing up. For example I need actually 1:40 minutes for a Einstein-WU. But BOINC says, that I will need over 2:36 hours. And this time is growing up with every finished WU... ID: 512183 ·

Richard Haselgrove Volunteer tester Send message Joined: 4 Jul 99 Posts: 14690 Credit: 200,643,578 RAC: 874	Message 512194 - Posted: 2 Feb 2007, 16:52:26 UTC - in response to Message 512183. On my C2D E6300 with Win XP Prof, iÃ‚Â´ve got a problem with 5.8.8. The estimated prcessor-time is growing up. For example I need actually 1:40 minutes for a Einstein-WU. But BOINC says, that I will need over 2:36 hours. And this time is growing up with every finished WU... This is an acknowledged bug, to be fixed in the "next" release. I'm really surprised they deemed this version as ready for public release, after the flurry of test releases every 2/3 days, some with feature sets included "by mistake". It didn't feel like an orderly progression towards stability. ID: 512194 ·

©2025 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.