@Skillz , if I change this, then all 10 of my hosts will need to be edited, and setup for my "Home" location will need to be changed to 8. Is it worth it for me ? I am now running over one million ppd.Note: Running 2 tasks at 8 CPU cores is showing at least twice as fast at 2 tasks at 16 cores on my 5950x.
I started out at 2 tasks at 16 CPUs and have now switched!
@Skillz , if I change this, then all 10 of my hosts will need to be edited, and setup for my "Home" location will need to be changed to 8. Is it worth it for me ? I am now running over one million ppd.
@Skillz , if I change this, then all 10 of my hosts will need to be edited, and setup for my "Home" location will need to be changed to 8. Is it worth it for me ? I am now running over one million ppd.
Do you have a Windows host or a Linux host?Note: Running 2 tasks at 8 CPU cores is showing at least twice as fast at 2 tasks at 16 cores on my 5950x.
I started out at 2 tasks at 16 CPUs and have now switched!
@cellarnoise and @Skillz already responded, but for completeness I add that it is even possible to change the thread count of an already running task: Suspend the task (to disk, not to RAM¹), let the boinc client read the new setting (if using the web preferences, not a local app_config.xml: trigger a project update in the client), resume the task. After that the client will likely still display the old thread count, but using a process viewer like the@Skillz , if I change this, then all 10 of my hosts will need to be edited, and setup for my "Home" location will need to be changed to 8. Is it worth it for me ? I am now running over one million ppd.
top console command — or viewing the respective "slots/*/stderr.txt" file — will show that the task is now running with the new setting.46.5 million lead now.
I'm glad you talked me into joining. Without my overwhelming power, the lead would only be 46.0 million, and that's just unacceptable..
Looks like while this works if you have an app_config.xml locally, it doesn't if the thread count was configured via the web preferences instead. In this case, shut down the client, edit the <cmdline> tag within the respective <app_version> block of the local client_state.xml file, restart the client.it is even possible to change the thread count of an already running task: Suspend the task (to disk, not to RAM¹), let the boinc client read the new setting (if using the web preferences, not a local app_config.xml: trigger a project update in the client), resume the task.
| Rank | Team | Credit |
|---|---|---|
| 1 | TeAm AnandTech | 168,187,145.77 |
| 2 | Antarctic Crunchers | 111,136,492.32 |
| 3 | SETI.Germany | 98,454,372.62 |
| 4 | AMD Users | 74,282,070.62 |
| 5 | Czech National Team | 70,509,782.32 |
| 6 | Ural Federal University | 38,615,552.63 |
| 7 | Aggie The Pew | 30,764,979.69 |
| 8 | BOINC@MIXI | 14,794,120.26 |
| 9 | Storm | 14,522,595.17 |
| 10 | BOINC@AUSTRALIA | 13,610,331.62 |
| # | Rank | User | Team | Credit |
|---|---|---|---|---|
| 1 | 2 | Skillz | TeAm AnandTech | 55,684,440.72 |
| 2 | 5 | xii5ku | TeAm AnandTech | 37,554,370.08 |
| 3 | 7 | parsnip soup in a clay bowl | TeAm AnandTech | 18,103,901.68 |
| 4 | 11 | crashtech | TeAm AnandTech | 15,881,337.25 |
| 5 | 13 | Icecold | TeAm AnandTech | 12,510,385.03 |
| 6 | 20 | markfw | TeAm AnandTech | 9,093,438.15 |
| 7 | 32 | emoga | TeAm AnandTech | 5,133,318.71 |
| 8 | 34 | biodoc | TeAm AnandTech | 4,913,476.87 |
| 9 | 49 | Orange Kid | TeAm AnandTech | 3,073,123.58 |
| 10 | 97 | Skivelitis2 | TeAm AnandTech | 1,348,149.27 |
| 11 | 111 | HutchinsonJC | TeAm AnandTech | 1,171,093.90 |
| 12 | 116 | Ken_g6 | TeAm AnandTech | 1,072,463.98 |
| 13 | 152 | Fardringle | TeAm AnandTech | 711,971.62 |
| 14 | 178 | cellarnoise2 | TeAm AnandTech | 541,459.08 |
| 15 | 184 | thigobr | TeAm AnandTech | 512,155.35 |
| 16 | 188 | Lane42 | TeAm AnandTech | 499,912.37 |
| 17 | 253 | SlangNRox | TeAm AnandTech | 172,783.05 |
| 18 | 280 | Kiska | TeAm AnandTech | 124,477.28 |
| 19 | 296 | Howdy | TeAm AnandTech | 84,887.81 |
| Generalized Cullen/Woodall (LLR) -- "llrGCW" | ||
|---|---|---|
| Platform | Version | Installation time |
| Microsoft Windows (Vista or later) running on an Intel x86-compatible CPU | 9.01 (mt) | 7 Dec 2020 | 20:22:53 UTC |
| Microsoft Windows (Vista or later) running on an AMD x86_64 or Intel EM64T CPU | 9.02 (mt) | 9 Sep 2021 | 9:18:29 UTC |
| Linux running on an Intel x86-compatible CPU | 9.01 (mt) | 7 Dec 2020 | 20:22:55 UTC |
| Linux running on an AMD x86_64 or Intel EM64T CPU | 9.02 (mt) | 9 Sep 2021 | 9:18:32 UTC |
| Mac OS 10.14+ running on an Intel 64-bit CPU | 9.01 (mt) | 7 Dec 2020 | 20:22:51 UTC |
On September 9 stream said:An update for GCW and SR5 projects.
New LLR2 (application version 9.02) is installed on these projects (major OS only - Linux/Windows 64-bit). It's built with more recent GWNUM version (30.x). For PrimeGrid users, the only noticeable difference is a new fast checkpoint loading code.
In old version, file loading is just awfully slow for tests where b<>2. It affects GCW and SR5 subprojects. A compression of checkpoints could lasts for many minutes, where compression itself takes just a few seconds, and rest was spent converting data from on-disk to in-memory formats. We worked around this problem as much as possible caching checkpoint data in memory, but it worked only if a whole test was finished uninterrupted. In new GWNUM, this problem was fixed and loading of files is now fast enough for any base. A compression of checkpoints at the end of test should be significantly faster even if test progress was interrupted.
This version already received sufficient testing on GFN server (it was used on GFN-MEGA and "LLR2 testing" for many months). Anyway, please report if you've noticed something unexpected or suspicious.
<name>sllr2_1.1.1_linux64_210204</name>
<download_url>http://www.primegrid.com/download/sllr2_1.1.1_linux64_210204.gz</download_url>