. . The RAC calculations are a strange and mystical thing. But if you are tracking your work output I suspect you will find it has not gone down, well certainly by that amount :)

The problem described has a lot to do with the sequence you get and process work. If you get work that's also given out to slower machines, your Pendings will go up , and RAC down, since your work will be validated more slowly than "normal". Thus. tonight I noticed that one of my machines had gone from 1340 pending to 1486 overnight, where the other is stable around 900 or so.

Ebbs and flows, at a much higher rate than I would expect statistically given the number of WUs processed daily, but there it is.

---

Oh, the Lunatics installers have never been a problem to use. Richard does a great job with them indeed. (Thanks, Richard.)
I suspect that if there is no newer version released by the end of next week, when my holiday vacation starts, I'll bite the bullet and install the latest that is available.

Hi kittyman, I think calling the Beta6 Lunatics installer a "beta" does it a disservice. As you alluded too.... picking final app versions to include in the installer seems to be a moving target. There always seems to be more tweaks that lead to the next numbered version. The r3557 SoG app I decided on for the BLC tasks seems to be very highly polished. Certainly haven't been any 'showstoppers' in its use. Very stable. Definitely have seen a boost in RAC and faster task completion in both BLC and Arecibo work compared to the last Lunatics Beta5 r3528 app. Its also more tuneable to eek out the very last drop in performance from your GPU's and system.

I don't think there will be any major performance upheavals until Petri's special CUDA6 app makes it to the Main project Windows apps. Then you will see CUDA tasks match or better the OpenCL tasks in head to head competition. Who knows when that hits a Lunatics installer? Just can hope for good things in the future year. My $0.02 in thinking.

Cheers

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

oops ... It's 03:40 (in the a.m.) and I awoke and realized I read the wrong column in my notes ... here is a reprint of the above with the correct numbers ...

This is correct BUT on my 770 moving from beta-5 (r3528) to beta-6 (r3557) on 11-9 my RAC dropped from 11,100.39 to 9,691.96
On 11-21. I re-installing beta-5 the rac began to climb to 10,766.33 on 12-5, I then did a system reconfiguration but the recovery appeared to be well on its way ... Oh well the good things never last ...

Ed F

It's true, using rac is a chancy business ... that's why I try to run a particular configuration for about a month. The recovery time was less than a month because the change over back to beta-5 was just an attempt to see if the month long downward trend would flatten or reverse. It clearly reversed direction (over the next 15 days) ... so I went on to my next "fun experiment". well I need to get back to sleep ... sorry for the mis-read of my notes!!

BTW this system is (almost) dedicated to SETI and the RAC's do stabilize after a 1 month time frame (+ or - ... say 300)

Ed F

P.S. the 770 is running on a dedicated cpu with NO tuning parameters used. on windows-7 core-7 (gen-1) boinc 6.12.34.[/quote]

BTW this system is (almost) dedicated to SETI and the RAC's do stabilize after a 1 month time frame (+ or - ... say 300)

I wish.
Depending on the work mix, my RAC can vary by up to 5,000 over a couple of weeks.

The only reliable way to see if one application is better than another (or not) is to check the run times for equivalent WUs.

---

Grant
Darwin NT

There is another thread for Lunatics installer and its discussion.
This thread exists for v8.19 apps support and information about their updates.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

New RC builds deployed at beta, please do test.

I have installed on 7953787. I noticed typical MB VM size is 170,000 vs. 210,000 for a system running r3528. Mem size is 166,000K vs 175,000K. CPU affinity is still ok. Here are some performance comparisons with previous app versions. All tests done on a FuryX with identical command line options:

Science_apps mb_cmdline.txt  :  -v 1 -instances_per_device 1 -sbs 1024 -period_iterations_num 1 -tt 300 -no_defaults_scaling -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 -hp  
 
WU: 30my10aa.2662.1294.4.31.WU 
ATi_HD5_r3330:     Elapsed 198.536 secs, CPU 122.500 secs
ATi_HD5_r3430:     Elapsed 192.207 secs, CPU 121.672 secs
ATi_HD5_r3486:     Elapsed 190.690 secs, CPU 121.844 secs
ATi_HD5_r3528:     Elapsed 246.433 secs, CPU 211.797 secs (Weakly similar)
ATi_HD5_r3584:     Elapsed 191.511 secs, CPU 122.125 secs
ATi_HD5_SoG_r3584: Elapsed 224.667 secs, CPU 196.813 secs
 
WU: blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.21012.0.17.26.147.WU 
ATi_HD5_r3330:     Elapsed 355.821 secs, CPU 125.781 secs
ATi_HD5_r3430:     Elapsed 356.056 secs, CPU 133.141 secs
ATi_HD5_r3486:     Elapsed 353.384 secs, CPU 130.359 secs
ATi_HD5_r3528:     Elapsed 355.592 secs, CPU 160.875 secs
ATi_HD5_r3584:     Elapsed 354.085 secs, CPU 132.031 secs
ATi_HD5_SoG_r3584: Elapsed 354.301 secs, CPU 158.656 secs

---

GitHub: Ricks-Lab
Instagram: ricks_labs

. . The RAC calculations are a strange and mystical thing. But if you are tracking your work output I suspect you will find it has not gone down, well certainly by that amount :)

The problem described has a lot to do with the sequence you get and process work. If you get work that's also given out to slower machines, your Pendings will go up , and RAC down, since your work will be validated more slowly than "normal". Thus. tonight I noticed that one of my machines had gone from 1340 pending to 1486 overnight, where the other is stable around 900 or so.

Ebbs and flows, at a much higher rate than I would expect statistically given the number of WUs processed daily, but there it is.

. . There are some participants in the project that have not optimised their setup in any way, and the dreaded "toe in the water" newbies who get a full cache of work, decide they are not really interested and opt out leaving the work in limbo. But such is life in the SETI project.

Stephen

.

BTW this system is (almost) dedicated to SETI and the RAC's do stabilize after a 1 month time frame (+ or - ... say 300)

I wish.
Depending on the work mix, my RAC can vary by up to 5,000 over a couple of weeks.

The only reliable way to see if one application is better than another (or not) is to check the run times for equivalent WUs.

. . Amen to that.

Stephen

.

New RC builds deployed at beta, please do test.

. .Hi Raistmer,

. . I am about to restore the GTX970s to my Pentium D rig (in place of the two GTX950s) but I do not want to completely withdraw that rig from processing tasks in Main. Is it possible to run both projects, Main and Beta-Testing, at the same time?

. . If it is I would like to run it as a 66/33 proposition with 66% running main. Any help, as always, is much appreciated.

Stephen

.

Hi,

I am trying to run Boinc client on a server I use to run Zoneminder for Security Cameras around the house. The CPU works fine for doing the projects, but I wanted to have the client use the GPU's of some spare cards I had around the house since it is a headless (no video / desktop) server and the GPU's were doing nothing.

So I have three ATI cards in the system, here is some system information below.

I have a few problems, concerns, questions. I am not a Linux guru, still learning a lot, but pretty good at Google. My problem is, I am not sure if these cards are functioning, compatible and functioning. I have tried to get the latest drivers installed, but it seems something changed in Ubuntu 16.04 and AMD / ATI cards and their support drivers etc. What I am trying to find out is if these cards GPU's will work and if I have the correct / best drivers, hoping a real guru can help out or a few :)

Another issue is my results:

Here is a link to a typical failed work unit for SETI. https://setiathome.berkeley.edu/result.php?resultid=5377275627

A link to the computer and it's work units: https://setiathome.berkeley.edu/results.php?hostid=8122337

I am not sure if these are coming from one of the cards, all of the cards, driver or what. Any ideas? Thanks!

Here is some info of the drivers the cards are using:

sudo lshw -c video
*-display
description: VGA compatible controller
product: Curacao PRO [Radeon R7 370 / R9 270/370 OEM]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:36 memory:e0000000-efffffff memory:f7800000-f783ffff ioport:b000(size=256) memory:f7840000-f785ffff
*-display
description: VGA compatible controller
product: Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:04:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:37 memory:d0000000-dfffffff memory:f7700000-f773ffff ioport:a000(size=256) memory:f7740000-f775ffff
*-display
description: VGA compatible controller
product: Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:05:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:38 memory:c0000000-cfffffff memory:f7600000-f763ffff ioport:9000(size=256) memory:f7640000-f765ffff




Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM]
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]



03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM]
Flags: bus master, fast devsel, latency 0, IRQ 36
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f7800000 (64-bit, non-prefetchable) [size=256K]
I/O ports at b000 [size=256]
Expansion ROM at f7840000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Subsystem: PC Partner Limited / Sapphire Technology Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at f7860000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] (prog-if 00 [VGA controller])
Subsystem: Hightech Information System Ltd. Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Flags: bus master, fast devsel, latency 0, IRQ 37
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at f7700000 (64-bit, non-prefetchable) [size=256K]
I/O ports at a000 [size=256]
Expansion ROM at f7740000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Subsystem: Hightech Information System Ltd. Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f7760000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] (prog-if 00 [VGA controller])
Subsystem: Hightech Information System Ltd. Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Flags: bus master, fast devsel, latency 0, IRQ 38
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at f7600000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 9000 [size=256]
Expansion ROM at f7640000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Subsystem: Hightech Information System Ltd. Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f7660000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

---