distributed.net staff keep (relatively) up-to-date logs of their activities in .plan files. These were traditionally available via finger, but we've put them on the web for easier consumption.
Behind the scenes, we are getting ready to move over to our newest project: OGR-28. This is to discover the most optimal Golomb Ruler with 28 marks. We anticipate that it will take about as long as OGR-27 has. It has some features in common with OGR-27: some of the packets will be very large (up to 1500 Gnodes), and there are three stub spaces. We expect that the first two stub spaces will take about 90 days to complete. Ask me about that last part in a few months time. :)
For the stats freaks among you, the number of stubs for each stubspace of OGR-28 is below:
Stubspace 1: 115676
Stubspace 2: 5823649
Stubspace 3: 518152118
It won’t be necessary for you to upgrade your client software, since OGR-27 clients are ready for OGR-28. If possible, though, I would recommend that you do have the most recent version. If you are running Windows 7 or 8 and your computer is less than four years old, that’s this one: http://http.distributed.net/pub/dcti/current-client/dnetc-win64-amd64.zip :)
If you are running something else, have a look on our download page: http://www.distributed.net/Download_clients
Once again, we will be sending some distributed.net swag to the lucky users who found the Optimal Golomb Ruler this time!
We’re very close being able to declare OGR-27 finished, but we have just a few more stubs remaining before final completion. The previous stubspaces 27.1, 27.2, and 27.3 are now officially complete. We expect the last results in 27.4 to be received some time in the next two weeks, and then hope to begin sending out the first OGR-28 stubs within a few hours after that.
As a reminder, no new dnetc client binaries or configuration will be necessary since all existing OGR-27 (OGR-NG) clients are already capable of working on OGR-28 once we begin sending out those workunits.
Look forward to us making another blog post containing some final statistics about OGR-27 within the next two weeks!
(edit: a previous version of this post had some overly optimistic dates)
We have completed over 96% of the work and are now close to wrapping up OGR-27. Some of you may have noticed some difficulty getting OGR packets earlier today, due to our need to begin recycling of the remaining stubs. As I write this, there are about 20 million left that need working on. It is likely that you may experience difficulty occasionally in the coming weeks when hoping to collect OGR stubs to process. This is due to the master key server being unable to speak and chew at the same time!
If you have a long memory, you may remember a note from me about needing to complete one more verification pass on a small number of stubs, about 2.2% of the total, that had been processed by buggy client versions. Now is the time! Some of you are already working on these stubs. One of our core contributors “Stream” has calculated that it will take us about 3 weeks at our current average (400 Gnode/sec) to complete the verification of the earlier stub spaces.
Today we also mark the 4000th day that we have been working on the RC5-72 project. We passed 3% completion only a few weeks ago and continue to make steady progress.
As ever, you can catch up with us in #distributed on IRC (irc.distributed.net).
Do you have an Android device on your desk languishing on charge while
you are asleep? Perhaps you have a shiny new tablet? It is now
possible to run OGR on it! Late to the dance, I know…
It is running using the BOINC Wrapper technology. You can download the
BOINC app from Google Play or the ‘Market’ app (depending on your OS
version.) Just attach it to the yoyo@home project:
http://www.rechenkraft.net/yoyo/ and follow the instructions.
It has been a while since I have posted any updates to my blog here. I’ve even had a few notes asking if we’re still working on our projects. I can assure you that we are.
We’re going full speed ahead on OGR. My favourite web page at the moment is http://stats.distributed.net/project/ogr_status.php?project_id=27 , which shows in detail how many stubs we have left to process until OGR-27 is complete.
At the same time, we’re still working on RC5-72; where we have nearly completed 3% of the total work space. We released new client software over the summer which works around the incompatibility we had with AMD 7xxx series graphics cards. The keyrate history graphs for RC5-72 and OGR (http://stats.distributed.net/keyrate.php?project_id=27 and http://stats.distributed.net/keyrate.php?project_id=8) are back online after a hardware failure.
I hope to have some more updates for you very soon. :)
If you have tried accessing www.distributed.net recently, you might have noticed that it was offline for nearly a full week. We unfortunately suffered from multiple hard disk failures just a couple of days apart on the RAID10 array of the machine that serves as our primary webserver, DNS server, and mail server. Ultimately, the disk array was unrecoverable and it will need to be recreated with new hard drives that we’ve just purchased. Fortunately, we have pretty recent backups of everything important so we’ve begun bringing the website and blogs back online using alternate hosting.
There are still a few minor things offline (bugzilla, email fetch/flush, email support, speeds database, project graphs) but we hope to have those all back online soon. We’re also taking this opportunity to improve our server infrastructure to minimize problems in the future. Of course during the website outage, the keymaster, keyserver network, and stats server continued to function and process blocks without interruption, so we expect that most of our participants were not noticeably impacted. Keep on crunching!
As you might remember, one year ago we participated in World IPv6 day by permanently turning on IPv6 access for our main website (www.distributed.net). Today, we made the next step towards embracing IPv6 by adding AAAA records to our proxy keyserver DNS addresses and by releasing our first set of IPv6-capable dnetc clients on our pre-release download page, as version v2.9111.520. There should be no additional client configuration changes needed for the client to utilize IPv6 once your OS has been properly configured.
At the moment, we only have one of our keyservers currently configured to handle IPv6 connections and our pre-release page only has IPv6 clients for Solaris/SunOS, however we will be adding more over the next few days. Updated personal proxies that support IPv6 will also be made available in the coming weeks. We welcome bug reports on bugs.distributed.net if you encounter any connectivity problems with our new releases.
Although Earth Day was a couple of weeks ago, we’ve been diligently “recycling” RC5-72 blocks (ie: re-distributing previously issued but unreturned work assignments) since last November. We realize that distributing these old blocks has been inconvenient for some of our users because the fragments are much smaller, causing more network and slightly lower keyrates, and we have appreciated everyone’s patience and understanding. Fortunately, we are very close to resuming work on fresh RC5-72 subspaces and will be able to send out larger, unfragmented blocks within the next day or so!
Keep on crunching!
After three years of effort, we have passed the half-way stage of this ground-breaking project. We thank you for your continued participation.
The following clients have been promoted to the list of officially released clients:
- Solaris/SunOS [x86] v2.9110.519
- OpenBSD [x86/ELF] v2.9110.519
- OpenBSD [AMD64/ELF] v2.9110.519
- FreeBSD [8.x/x86] v2.9110.519
- FreeBSD [7.x/x86/ELF] v2.9110.519
- FreeBSD [6.x/x86/ELF] v2.9110.519
- Linux [AMD64/Stream] v2.9110.519
- Linux [CellBE] v2.9110.519
- Linux [ARM/eabi] v2.9110.519
- Linux [x86/ELF/uclibc] v2.9110.519
- Linux [AMD64/ELF] v2.9110.519b
- Windows 64bit [AMD64] v2.9110.519b
- Windows 32bit [x86/Zipped] v2.9110.519b
- Windows 32bit [x86/CUDA-3.1] v2.9110.519b
They can be downloaded from http://www.distributed.net/Download_clients
The list of functional changes is at http://http.distributed.net/pub/dcti/current-client/CHANGES.txt