Posts by MarkJ

1) Message boards : Number crunching : Debian Project Warns: Turn off Hyperthreading with Skylake and Kaby Lake (Message 1875372)
Posted 14 hours ago by Profile MarkJProject Donor
Post:
Thanks for the post. I have 8 of them. All got patched this morning.

Debian have a package called Intel-microcode available in both Stretch and jessie-backports. From what I understand the microcode is a partial fix and you also need a BIOS update.
2) Message boards : Number crunching : Validation pending.... (Message 1872518)
Posted 16 days ago by Profile MarkJProject Donor
Post:
The size of your local cache has no significant impact on the number of "pending" results. The number pending is totally dependent on the relative turnarounds of you and your wingmen.

Because you have less in the cache they turn around faster. Sure they take the same amount to time to run but they spend less time in a "ready to start" state. Think of those people who have 5 and 10 day caches, that's around 4.5 to 9.5 days before they even start them.

The drawback is of course when there is an outage (like every Tuesday) you could run out of work but that's what other projects are for.

I agree with you regarding the error and invalid rates, they are more important than how many are pending.
3) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1872517)
Posted 16 days ago by Profile MarkJProject Donor
Post:
We don't tend to reinstall very often. For what Tbar, Petri and Jason do it would make sense but for the average to slightly advanced users we want to install it and have it run. There is the occasional app update to take care of but that is pretty much it. I take the KISS principle, if I can get most of the bits from a repo then that's one less thing for me to stuff up.

I've switched my entire farm from Windows to Linux apart from a daily driver laptop. A process that is repeatable and reliable is the way to go. If I got a new machine today I could have it up and running in say an hour with exactly the same setup as all the others apart from hardware differences.
4) Message boards : Number crunching : Validation pending.... (Message 1872418)
Posted 16 days ago by Profile MarkJProject Donor
Post:
I've got 2761 when I checked just now. That's out of 4595 so more than 50% are waiting. I run pretty small caches. A couple of my machines are running the cuda80 app which is quick.
5) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1872415)
Posted 16 days ago by Profile MarkJProject Donor
Post:
Post the step by step guide here.

Its on the second page of this thread. It can also be found here

It doesn't cover the copying app_info and apps to the project folder but if you need that part I sure I can knock up something. I normally use a USB thumb drive and just drag and drop the files using the gui.
6) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1872383)
Posted 16 days ago by Profile MarkJProject Donor
Post:
Why pick the most complicated way of doing it?

You could do a bog-standard Debian install and get everything from the repos apart from the CUDA app. You get a more up to date BOINC client (7.6.33) which has improved CUDA detection and a more up to date CUDA driver (375.66). The only complex bit would be doing the app_info and apps into the project folder.
7) Message boards : Number crunching : Restarting BOINC Manager (Message 1872209)
Posted 17 days ago by Profile MarkJProject Donor
Post:
I"m running Debian. I added the boincmgr to the desktop. In its properties I specified the password to the core client. That is the same password thats in /var/lib/boinc-client/gui_rpc_auth.cfg unless its blank.
8) Message boards : Number crunching : New Linux Trojans installs crypto currency mining software on Raspberry Pi (Message 1871948)
Posted 18 days ago by Profile MarkJProject Donor
Post:
You wouldn't think a Pi would produce much in the way of crypto currency. I have a bunch of Pi's and the first thing I do after imaging them is to change their password.

I did read one tutorial where the guy wanted to run it as a web server so he deleted the default user account. That sounds like a good idea now. For some reason though he didn't put a firewall on it.
9) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1871739)
Posted 19 days ago by Profile MarkJProject Donor
Post:
For those that went with Debian they've just put the 375.66 drivers into Jessie-backports. All I did to upgrade was:

1. Login as root
2. In a terminal type "service boinc-client stop"
3. Type "apt update" to get the latest list of packages
4. Type "apt upgrade -y" to update it. It pops up a warning about older drivers. Just press enter to continue
5. After its finished (it takes about 5 mins to compile) type "sync" to flush to disk
6. Type "reboot" to reboot the machine

My original instructions for setting up a Linux CUDA cruncher using Debian can be found here
10) Message boards : Number crunching : Do we have more data than volunteers? (Message 1871455)
Posted 21 days ago by Profile MarkJProject Donor
Post:
Speculation is pointless, I have a good reason to do this and SETI@Home serves the purpose. I may do more, as this is only a few racks in one row of several in my data center. It's only temporary, will end when it ends. Enjoy the fireworks.

I will say that I am not interested in competing against anyone. I just happen to like SETI@Home, even though I know the odds of it finding what it is looking for are infinitesimal.

Oh don't get me wrong I'm in this for science and am more than happy you've dedicated your machines to the search.

I'm just a little envious of your data center compared to my small farm. Unfortunately I'm constrained by available space, power and finances.
11) Message boards : Number crunching : Do we have more data than volunteers? (Message 1871223)
Posted 22 days ago by Profile MarkJProject Donor
Post:
I'll take up some of the slack. Just brought 7000+ cores online on SETI@Home. The reason why is hilarious, but unfortunately I can't share it here.

Something like management want to stress test the disaster recovery site? Sounds like more cores than the Atlas cluster that Einstein use.

They aren't the latest kit but a year or two old judging by the Xeon v2 and v3's. Hate to think what the electricity bill would be like.

I need a shed like Wiggo, my loft gets too hot even in winter 😩
12) Message boards : Number crunching : CES 2017 -- AMD RYZEN CPU (Message 1871092)
Posted 23 days ago by Profile MarkJProject Donor
Post:
I've got a couple of Ryzen 1700's running such as this one running Linux. My current quandary is if I should replace the 1700's with 1700x or not. Apart from the initial cost of buying another CPU there is an extra 30 watts for the 1700x for about a 10 to 12% gain in productivity.

I did some experiments with the Einstein gravity wave tuning run on them. Running 16 at a time average run time was 33,000 to 37,000 seconds, when I limit it to 8 via an app_config they came in at 20,000 seconds. The app was their AVX and it got the Lo work units.

My current experiment is to see if leaving a single thread free improves performance or not. I'm running a single GPU with the Seti CUDA80 app so it can make use of the available thread but certainly doesn't need its own as it sleeps a fair bit (according to top).
13) Message boards : Number crunching : AMD's Upcoming Ryzen R9 "Threadripper" 16-core, 32-thread CPU (Message 1868334)
Posted 20 May 2017 by Profile MarkJProject Donor
Post:
For a no-cost solution reducing the deadline would help reduce the database bloat that needs frequent compression? While it may have an effect on the slower rigs they could run a smaller cache so they can meet the deadline.

Currently over at Einstein they're doing a Gravity wave tuning run with a 5 day deadline. Now that's obviously not practical for normal use but it certainly clears the tasks a lot quicker. Maybe 10 to 21 days is a better number to use.
14) Message boards : Number crunching : Help with Intel GPU on Arch Linuc (Message 1866694)
Posted 11 May 2017 by Profile MarkJProject Donor
Post:
I am running Debian. When I set up mine I had to get beignet 1.3.0 (beignet-opencl-icd) from Jessie backports to support the HD Graphics 530. I also needed to get boinc-client-opencl from there. You don't need mesa.

Given you're running Arch I am not sure how up to date their repos are.

As mentioned above running the iGPU will slow down the rest of the CPU tasks so its usually not worth the effort.
15) Message boards : Number crunching : You have to love early Xmas and B'day presents (even if you have to pay for them yourself). (Message 1864716)
Posted 30 Apr 2017 by Profile MarkJProject Donor
Post:
I've converted the farm to Linux. Up until Friday the two GTX1060's were running the Petri special and then I decommissioned the machines. I'm selling them off to get a couple of Ryzen's and the two GTX1060's will go in them.

In the mean time I have a couple of i3's running a GTX970 each with Petri special. I've ordered another pair of 1060's which will replace the 970's in order to cut down the electricity use a bit. Its nowhere near Christmas but that's my present to myself :-)
16) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1861775)
Posted 16 Apr 2017 by Profile MarkJProject Donor
Post:
I got the cuda libraries that Petri posted earlier in this thread and put them in the /var/lib/boinc-client directory. They may not be needed. Make sure they're marked as executable and are owned by user boinc (do a chown boinc:boinc lib* command).

Apparently you don't need these to get it to recognise CUDA. You will of course need to put them and the app into the projects/setiathome folder along with an app_info.
17) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1861619)
Posted 15 Apr 2017 by Profile MarkJProject Donor
Post:
Rather than using an outdated Ubuntu this is what I used with Debian. This will get you the latest Debian (Jessie), latest kernel (4.9) and the 7.6.33 BOINC client. This won't give you the CUDA80 app but you should be up and running with a CUDA capable machine after doing this.


Part 1 - Install Debian
I used the Debian 8.7 net install for this. You’ll need a thumb drive or a blank CD. Download it from http://www.debian.org/distrib/ and write the ISO image to CD or thumb drive.

Boot off the thumb drive or CD. It will start up the Debian installer

Install Debian select, SSH server and whatever desktop you prefer and remove all other selections. Once done it will reboot.


Part 2 - Install Nvidia software
Login as root, open a xterm window and type the following commands:

cd /etc/apt

nano sources.list (nano is a text editor)

Change “Jessie Main” lines to “jessie main contrib non-free” and add a Jessie-backports line. It should look like this when you're done. I'm using httpredir as it will pick the fastest server.

deb http://httpredir.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb http://httpredir.debian.org/debian/ jessie-updates main contrib non-free
deb http://httpredir.debian.org/debian/ jessie-backports main contrib non-free

Exit out of nano and save the file (Control-O followed by Control-X)

apt update

apt install –t jessie-backports firmware-realtek (if needed)

apt install –t jessie-backports linux-image-amd64

apt install –t jessie-backports nvida-kernel-dkms nvidia-smi nvidia-xconfig

apt install –t jessie-backports nvidia-opencl-icd (if you want OpenCL support)

nvidia-xconfig

sync

reboot


Part 3 – Install BOINC
login as root. Start xterm again and type the following commands:

apt install –t Jessie-backports boinc-nvidia-cuda boinc-manager

I got the cuda libraries that Petri posted earlier in this thread and put them in the /var/lib/boinc-client directory. They may not be needed. Make sure they're marked as executable and are owned by user boinc (do a chown boinc:boinc lib* command).

sync

reboot
18) Message boards : Number crunching : Water cooling the Breakthrough Listen CPUs and GPUs (Message 1861191)
Posted 13 Apr 2017 by Profile MarkJProject Donor
Post:
My GPU's are running on air. If I drool it will be a mixture of air and water :)

P.

Ahh a hybrid setup
19) Message boards : Number crunching : Looking for Linux x64 optimized apps (Message 1859180)
Posted 2 Apr 2017 by Profile MarkJProject Donor
Post:
An update on this. I have swapped all my iGPU machines over to Linux. While I have beignet installed I haven't defined an OpenCL app in my app_info as it slows the rest of the CPU tasks down. For the moment they're running as CPU only rigs. I have defined the astropulse app as well but AP work units are as rare as hens teeth :-)
20) Message boards : Number crunching : CES 2017 -- AMD RYZEN CPU (Message 1852763)
Posted 4 Mar 2017 by Profile MarkJProject Donor
Post:
I'm waiting delivery of a 1700, Asus x370 pro motherboard and 8GB RAM.

I think you may find that too little memory unless its only running Seti.

I had to upgrade the memory in all my i7-6700's to 16Gb to run the Einstein OM1CV work units, They can use up to 1.5Gb per work unit. Some of the VM based work units from other projects can also be a memory hog from what I hear, so I am ordering 32Gb with mine.


Next 20


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