1)
Message boards :
Number crunching :
SETI orphans
(Message 2072886)
Posted 8 Apr 2021 by StFreddy Post: You can compare your wcg opng results with your wingman: under your account, click Results Status, then click on the name of the workunit in the Result name column. You will see your wingman here. Click on the Valid link in the Status column. |
2)
Message boards :
Number crunching :
GPU FLOPS: Theory vs Reality
(Message 2023732)
Posted 19 Dec 2019 by StFreddy Post: Tom, if you want to have an idea how a gtx1660 (non ti and non super) performs, check my host: ID: 8838390 This PC uses the special sauce. The CPU is mostly crunching WCG, occasionally SETI. The GPU only crunches SETI 7/24, RAC is around 50k. The GPU alone consumes 90 Watts while crunching SETI. It is pretty efficient. |
3)
Message boards :
Number crunching :
Anything relating to AstroPulse (3) tasks
(Message 2021075)
Posted 29 Nov 2019 by StFreddy Post: thanks for the suggestions to everyone. Its still a mystery why the nvidia module has disappeared after a simple a reboot, but now, as Keith suggested, I reverted back to nouveau driver and the machine is crunching again. Also there are some AP tasks completed and validated by this host. To be honest, I don't want to mess anything with this host, because it is working as intended, although it is still using the nouveau driver. Is there any advantage to use ppa nvidia drivers? Thanks. |
4)
Message boards :
Number crunching :
Anything relating to AstroPulse (3) tasks
(Message 2020263)
Posted 23 Nov 2019 by StFreddy Post: my system totally crashed. I only have command prompt (SSH). Nvidia driver still not seen by ubuntu. ferike@ferike-linux:~$ uname -a Linux ferike-linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ferike@ferike-linux:~$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ferike@ferike-linux:~$ clinfo Number of platforms 0 Although if I issue sudo apt purge *nvidia* then it seems it would remove the following packages: The following packages were automatically installed and are no longer required: dkms libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm8:i386 libnvidia-compute-430:i386 libnvidia-decode-430:i386 libnvidia-encode-430:i386 libnvidia-fbc1-430:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386 libxxf86vm1:i386 pkg-config screen-resolution-extra xserver-xorg-core-hwe-18.04 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: libnvidia-cfg1-430* libnvidia-common-430* libnvidia-compute-430* libnvidia-decode-430* libnvidia-encode-430* libnvidia-fbc1-430* libnvidia-gl-430* libnvidia-gl-430:i386* libnvidia-ifr1-430* libnvidia-ifr1-430:i386* nvidia-compute-utils-430* nvidia-dkms-430* nvidia-driver-418* nvidia-driver-430* nvidia-kernel-common-430* nvidia-kernel-source-430* nvidia-prime* nvidia-settings* nvidia-utils-418* nvidia-utils-430* xserver-xorg-video-nvidia-430* 0 upgraded, 0 newly installed, 21 to remove and 0 not upgraded. After this operation, 395 MB disk space will be freed. so if i understand this correctly, the driver is installed. I used the ppa method to install nvidia driver. Tried 390, 410, 440. Nothing works. Did someone face similar issues? |
5)
Message boards :
Number crunching :
Anything relating to AstroPulse (3) tasks
(Message 2020252)
Posted 23 Nov 2019 by StFreddy Post: I already had everything installed, then rebooted. Now nvidia drivers are not recognized. I will need to connect a display and check what is happening. Damn. |
6)
Message boards :
Number crunching :
Anything relating to AstroPulse (3) tasks
(Message 2020247)
Posted 23 Nov 2019 by StFreddy Post: can someone help please. All AP wu-s are errored out on my linux machine with message: 201 (0x000000C9) EXIT_MISSING_COPROC searched for solution in forum threads, but got no luck. I want my gtx1660 to crunch AP. ferike@ferike-linux:~$ clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform Version OpenCL 1.2 CUDA 10.2.120 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer Platform Extensions function suffix NV Platform Name NVIDIA CUDA Number of devices 1 Device Name GeForce GTX 1660 Device Vendor NVIDIA Corporation Device Vendor ID 0x10de Device Version OpenCL 1.2 CUDA Driver Version 430.26 Device OpenCL C Version OpenCL C 1.2 Device Type GPU Device Topology (NV) PCI-E, 26:00.0 Device Profile FULL_PROFILE Device Available Yes Compiler Available Yes Linker Available Yes Max compute units 22 Max clock frequency 1785MHz Compute Capability (NV) 7.5 Device Partition (core) Max number of sub-devices 1 Supported partition types None Max work item dimensions 3 Max work item sizes 1024x1024x64 Max work group size 1024 Preferred work group size multiple 32 Warp size (NV) 32 Preferred / native vector sizes char 1 / 1 short 1 / 1 int 1 / 1 long 1 / 1 half 0 / 0 (n/a) float 1 / 1 double 1 / 1 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations Yes Double-precision Floating-point support (cl_khr_fp64) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Address bits 64, Little-Endian Global memory size 6232014848 (5.804GiB) Error Correction support No Max memory allocation 1558003712 (1.451GiB) Unified memory for Host and Device No Integrated memory (NV) No Minimum alignment for any data type 128 bytes Alignment of base address 4096 bits (512 bytes) Global Memory cache type Read/Write Global Memory cache size 360448 (352KiB) Global Memory cache line size 128 bytes Image support Yes Max number of samplers per kernel 32 Max size for 1D images from buffer 134217728 pixels Max 1D or 2D image array size 2048 images Max 2D image size 32768x32768 pixels Max 3D image size 16384x16384x16384 pixels Max number of read image args 256 Max number of write image args 32 Local memory type Local Local memory size 49152 (48KiB) Registers per block (NV) 65536 Max number of constant args 9 Max constant buffer size 65536 (64KiB) Max size of kernel argument 4352 (4.25KiB) Queue properties Out-of-order execution Yes Profiling Yes Prefer user sync for interop No Profiling timer resolution 1000ns Execution capabilities Run OpenCL kernels Yes Run native kernels No Kernel execution timeout (NV) Yes Concurrent copy and kernel execution (NV) Yes Number of async copy engines 3 printf() buffer size 1048576 (1024KiB) Built-in kernels Device Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer NULL platform behavior clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) NVIDIA CUDA clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [NV] clCreateContext(NULL, ...) [default] Success [NV] clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) Invalid device type for platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) No platform ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.2.11 ICD loader Profile OpenCL 2.1 OS is Ubuntu 18.03 LTS. thanks in advance. This is the machine: https://setiathome.berkeley.edu/show_host_detail.php?hostid=8838390 |
7)
Message boards :
Number crunching :
SETI/BOINC Milestones [ v2.0 ] - XXIX
(Message 2019937)
Posted 21 Nov 2019 by StFreddy Post: just passed 10 million. My GTX 1660 helps a lot with the linux cuda app. |
8)
Message boards :
Number crunching :
Ryzen and Threadripper
(Message 2017722)
Posted 3 Nov 2019 by StFreddy Post: The TDP of a 3700X is 65watts. The TDP of a 2700X is 105watts. So I expect the 3700X to be more power efficient at the same clocks. I think these TDP values are true, when core performance boost is disabled. When core performance boost (not PBO or AutoOC!) is enabled, core package power rises significantly: my 3900x eats 145W with core performance boost enabled (without PBO and AutoOC). The TDP is 105W according to AMD. (if you do manual overclock without undervolting, power consumption will rise further) With -0.064V undervolt max core package power decreased to ~130W under World Community Grid. Noctua NH-d15s can keep this beast around 75-77 Celsius under 75% WCG load, which is fine I think. If you disable core performance boost, your CPU will operate only on its base clock and won't boost. You will loose performance, but its package power consumption will be close to the advertised TDP value. |
9)
Message boards :
Number crunching :
Ryzen and Threadripper
(Message 2015086)
Posted 11 Oct 2019 by StFreddy Post: What temperatures are normal for a 3900x while crunching? Mine reaches 80 Celsius using the avx app. Is it safe? Cooler is a noctua nh d15s. |
10)
Message boards :
Number crunching :
Vega 56 optimal settings
(Message 2009598)
Posted 28 Aug 2019 by StFreddy Post: Just wondering if someone has any experience with vega 56/64... Do you guys underclock/undervolt your gpus to save power while crunching? Have a look at this thread: https://setiathome.berkeley.edu/forum_thread.php?id=84209 lots of useful information there. |
11)
Message boards :
Number crunching :
Examples of AMD Gpu commandlines - FAQ
(Message 2009379)
Posted 26 Aug 2019 by StFreddy Post: I have a Vega56 and it turned out that my overclocked Ryzen 1800x CPU is more efficient under Seti than my Vega56 undervolted and using optimized ATI app (and command line parameters) under Windows. If you don't care about efficiency (I mean performance/watts) than give it a try, it can do about 20k RAC I guess. But with constant 180-200W power consumption. Not a good deal. |
12)
Message boards :
Number crunching :
Ryzen and Threadripper
(Message 2003596)
Posted 21 Jul 2019 by StFreddy Post: Keith, Isn't 80° C too much for this chip? I don't like seeing my 1800x above 70° C... I know 7nm ryzens begin to throttle at around 90° C , but I don't know if it will shorten the life of the CPU if being continuously used around 80° C. |
13)
Message boards :
Number crunching :
Ryzen and Threadripper
(Message 2003467)
Posted 20 Jul 2019 by StFreddy Post: Keith, What temperatures are you measuring using the AVX app on your 3900x? What cooler do you use on that beast? How many CPU tasks are you running in parallel? I am planning to swap my 1800x to a 3900x but I see temperatures are problematic... |
14)
Message boards :
Number crunching :
Don't know where it should go? Stick it here!
(Message 1997392)
Posted 8 Jun 2019 by StFreddy Post: just found this, may be interesting for people running Ryzen/Threadripper under Linux: https://www.reddit.com/r/linux/comments/9djs3b/monitoring_the_power_consumption_of_amd_ryzen_and/ |
15)
Message boards :
Number crunching :
Examples of AMD Gpu commandlines - FAQ
(Message 1994013)
Posted 17 May 2019 by StFreddy Post: I used both Mike's and Rueike's command line parameters on my undervolted Vega56. Not much difference, just few seconds. OS: windows 10. Based on my findings, a Ryzen 1800x @3.9GHz (1.25V) is much more efficient than my Vega 56: roughly the same RAC with lower power consumption (blc33): - Vega56: ~19k RAC/day, ~150W power consumption - Ryzen 1800x: ~19k RAC/day , ~105W power consumption this is under windows 10 with the latest Lunatics Apps installed. This is why I won't use this Vega for Seti any more. Maybe I will find another project for Vega where it may be more efficient. |
16)
Message boards :
Number crunching :
How many gpus can you run on an AMD AM4 socket motherboard? (Ryzen 7 1900, 2700 etc)
(Message 1993134)
Posted 8 May 2019 by StFreddy Post: try 1.35V cpu core fixed and 4.0 GHz on all cores manually. Should be fine, but needs to be tested. If its stable, lower the cpu voltage. Hopefully you have some good cooling on the CPU though. |
17)
Message boards :
Number crunching :
My 2990WX
(Message 1966887)
Posted 24 Nov 2018 by StFreddy Post: I think the best motherboard for your beast is: https://www.msi.com/Motherboard/MEG-X399-CREATION Maximum Power: 19 phases digital power with heat-pipe heatsink design I wouldn't try overclocking above 3.8GHz without this mobo. |
18)
Message boards :
Number crunching :
My 2990WX
(Message 1966878)
Posted 24 Nov 2018 by StFreddy Post: one more comment on the RAM: Based on your MB's QVL here: https://www.msi.com/Motherboard/support/X399-GAMING-PRO-CARBON-AC#support-mem-17 you can see anything above 3000MHz needs 1.35V. |
19)
Message boards :
Number crunching :
My 2990WX
(Message 1966789)
Posted 23 Nov 2018 by StFreddy Post:
as far as I read on different forums, for ddr 3200MHz, 1.35V is recommended on Ryzen systems. Not sure about threadripper, but I think that 1.2V is simply not enough. On the other hand, you are modifying too much parameters at once. Put your CPU back to its factory default settings and test RAM stability first. Use memtest86. If that's stable, move forward with the CPU. BUT, keep in mind that your CPU is YERY power hungry. I am not sure if your motherboard can handle that amount of power if you overclock. Just run it on default settings for a few days. After that, increase 100MHz, then test for a few days. I wouldn't try that 4.0GHz all core overclock. your motherboard's VRM can be a weak point. |
20)
Message boards :
Number crunching :
GPU FLOPS: Theory vs Reality
(Message 1963767)
Posted 7 Nov 2018 by StFreddy Post: Now completion times stabilize around 220 seconds for blc01 tasks. If I get ~50 credits for a single task, then it is roughly 800 credits/hour using 140W/h power on average. Not as bad as I thought. I didn't expect such throughput/efficiency based on the diagram that Shaggie76 posted on the previous page. Thanks Mike and Tom for the tips. |
©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.