Farm status
Intel GPUs
One running Einstein Gravity Wave work
Nvidia GPUs
All running Einstein Gravity Wave work
Raspberry Pis
All except two running Einstein BRP4 work
For news on the Raspberry Pis see Marks Rpi Cluster
Other news
Last week I mentioned issues installing ZFS. I raised a bug report with Debian. A work around was posted for the installer issue and I have now got ZFS running on one of the storage servers. I haven't tried the other one yet but expect the same process will work on it.
Also last week I tried updating one of the Nvidia GPU machines to Debian Buster, their current release. It locks up while booting but can be accessed via ssh. From there I can install the Nvidia drivers. It will boot after that but the screen will only do 1024x768 resolution. I raised another bug for Debian. In the mean time I have gone back to running Debian Stretch which works fine.
CPDN announced on the 18th of June they were going to run the OpenIFS climate models. Normally they run 32 bit versions of the UK Met Office climate models. Since then I increased the memory in the Intel GPU machines to be able to run these. We're still waiting for these climate models to become available.
28 September 2019
14 September 2019
14th of September
Farm status
Intel GPUs
One running Einstein Gravity Wave work
Nvidia GPUs
All four running Einstein Gravity Wave work
Raspberry Pis
All except two running Einstein BRP4 work
For news on the Raspberry Pis see Marks Rpi Cluster
Other news
I've been working on one of two storage servers for the past two weeks. Its a hard disk based server in a 2U rack mount case. Hardware wise its all working, but the software is causing problems. I can't get ZFS installed on it. It fails to build. I've tried different Debian releases and all of them seem to be broken. I bought this one almost a year ago. It was intended to replace my current (tower case) server which has less drive bays, thus limited scope for expansion.
I mentioned two storage servers. The other one is a NVMe based one in a 1U rack mount case. Apart from the fans being really loud and annoying its hardware also works fine. It too needs to run ZFS so I have been trying to get the quieter one going first.
I have updated the Intel GPU machines to Debian Buster. Unfortunately Buster locks up on the Nvidia GPU machines and won't even give a logon prompt. Time to raise another bug with Debian.
Intel GPUs
One running Einstein Gravity Wave work
Nvidia GPUs
All four running Einstein Gravity Wave work
Raspberry Pis
All except two running Einstein BRP4 work
For news on the Raspberry Pis see Marks Rpi Cluster
Other news
I've been working on one of two storage servers for the past two weeks. Its a hard disk based server in a 2U rack mount case. Hardware wise its all working, but the software is causing problems. I can't get ZFS installed on it. It fails to build. I've tried different Debian releases and all of them seem to be broken. I bought this one almost a year ago. It was intended to replace my current (tower case) server which has less drive bays, thus limited scope for expansion.
I mentioned two storage servers. The other one is a NVMe based one in a 1U rack mount case. Apart from the fans being really loud and annoying its hardware also works fine. It too needs to run ZFS so I have been trying to get the quieter one going first.
I have updated the Intel GPU machines to Debian Buster. Unfortunately Buster locks up on the Nvidia GPU machines and won't even give a logon prompt. Time to raise another bug with Debian.
25 August 2019
25th of August
Farm status
Intel GPUs
All off
Nvidia GPUs
Have been running Seti, now running Einstein.
Raspberry Pis
Running Einstein BRP4 work
Other news
I assembled the 4th Ryzen 3600 (aka GPU compute node v3) machine and have had it running in. I also have it on a power point power meter to see how much juice they use. At peak load with the CPU and GPU fully utilised it jumped to 240 watts (at a supposed 240 volts - according to the meter its getting 236 volts). Running Milkyway work on the GPU is less taxing and it barely gets to 200 watts. Running just the CPU at full load its using 140 watts. Idle was 60 watts.
It was a bit warmer yesterday afternoon so I had to stop GPU crunching, hence running Einstein gravity wave work on the CPU only. The Ryzen 3600 is faster than my i7-8700 machines doing the same work. Both CPU's have the same core count but the Intel has a lower clock speed (3.2GHz base) and doesn't support memory faster than 2666MHz.
Intel GPUs
All off
Nvidia GPUs
Have been running Seti, now running Einstein.
Raspberry Pis
Running Einstein BRP4 work
Other news
I assembled the 4th Ryzen 3600 (aka GPU compute node v3) machine and have had it running in. I also have it on a power point power meter to see how much juice they use. At peak load with the CPU and GPU fully utilised it jumped to 240 watts (at a supposed 240 volts - according to the meter its getting 236 volts). Running Milkyway work on the GPU is less taxing and it barely gets to 200 watts. Running just the CPU at full load its using 140 watts. Idle was 60 watts.
It was a bit warmer yesterday afternoon so I had to stop GPU crunching, hence running Einstein gravity wave work on the CPU only. The Ryzen 3600 is faster than my i7-8700 machines doing the same work. Both CPU's have the same core count but the Intel has a lower clock speed (3.2GHz base) and doesn't support memory faster than 2666MHz.
11 August 2019
11th of August
Farm status
Intel GPUs
All off
Nvidia GPUs
Three running Seti
Raspberry Pis
All running Einstein BRP4 work
GPU compute nodes
Version 2 of the GPU compute nodes was a Ryzen 1700 with a GTX 1660 Ti (they originally had GTX 1060's but I upgraded them to the 1660 Ti when they came out). Version 3 is a Ryzen 3600 with the same GTX 1660 Ti.
I got another two GTX 1660 Ti's and have assembled another of the v3 GPU compute nodes. I also decommissioned another v2 as well as an i3-6100t that was acting as a GPU compute node (with a GTX 1060). I still have one more v3 to assemble and one more Ryzen 1700 to decommission. I will be selling off the older compute nodes.
The first v3 GPU compute node that I built has managed to get its recent average up to 73,400 so far for Seti. They take a bit over a month to reach their highest average and this one has been going just shy of one month. The second v3 GPU compute node that I built has got up to a recent average of 53,300 and its only been running for two weeks.
With just three GPU compute nodes running I've climbed to 61st place on the Seti rankings. I don't expect it to last too long though as once the first v3 GPU compute node is a month old I will get it doing some Einstein CPU work.
Intel GPUs
All off
Nvidia GPUs
Three running Seti
Raspberry Pis
All running Einstein BRP4 work
GPU compute nodes
Version 2 of the GPU compute nodes was a Ryzen 1700 with a GTX 1660 Ti (they originally had GTX 1060's but I upgraded them to the 1660 Ti when they came out). Version 3 is a Ryzen 3600 with the same GTX 1660 Ti.
I got another two GTX 1660 Ti's and have assembled another of the v3 GPU compute nodes. I also decommissioned another v2 as well as an i3-6100t that was acting as a GPU compute node (with a GTX 1060). I still have one more v3 to assemble and one more Ryzen 1700 to decommission. I will be selling off the older compute nodes.
The first v3 GPU compute node that I built has managed to get its recent average up to 73,400 so far for Seti. They take a bit over a month to reach their highest average and this one has been going just shy of one month. The second v3 GPU compute node that I built has got up to a recent average of 53,300 and its only been running for two weeks.
With just three GPU compute nodes running I've climbed to 61st place on the Seti rankings. I don't expect it to last too long though as once the first v3 GPU compute node is a month old I will get it doing some Einstein CPU work.
Subscribe to:
Comments (Atom)