logo  Collatz Conjecture
log in

Powered by BOINC

User of the day

User profile Profile T-Armstrong


Up and Running
Don't blame the cat sitter! The server was online all last week. It was the firewall that was down. Naturally, I didn't leave directions on how to check that.
Regardless of the reason, Collatz is once again available. Before bringing the firewall back online, I ran a query to get the number and type of work units in progress for each host so I can manually grant credit for them if cancelled by the server for being late even if the grace period has not yet passed.
16 Jun 2014, 14:24:36 UTC · Comment

Potential Outage After June 5 thru June 15
From June 5-15, the temporary Collatz system admin will be the cat sitter. That doesn't sound very reassuring does it? Sorry, but if the server goes down and requires anything other than a simple reboot, there may be an extended outage.

Unfortunately, the chances of that happening are higher than normal since Commonwealth Edison (a.k.a. ComEd, the electrical company in the area) failed to notify me on their original attempt to replace my power meter last week but were unable to do so since it evidently takes at least two people to do it. Since they didn't call before the last attempt, Murphy's Law suggests that they will not call before the next attempt and that it will take place while I am on vacation. The cat sitter doesn't know how to switch over to the generator if the outage exceeds the UPS battery so if the power is out for an extended period, Collatz may remain down until I get back.
27 May 2014, 2:54:44 UTC · Comment

Server Back Online
I had intended to get the routine maintenance done prior to the 2014 BOINC Pentathlon Sprint rather than during it but due to a PBCAK (problem between chair and keyboard also known as operator error) the Collatz server attempted to install software it shouldn't have during the routine scheduled maintenance and there were some nasty unforeseen results. After a kernel panic followed closely by me panicking and multiple attempts at repairing the corrupted libraries without having to re-install the entire operating system, Collatz is now back online. 8 May 2014, 14:00:59 UTC · Comment

Micro Collatz CPU Apps
A few people have requested Micro Collatz work units for CPUs on Windows and Linux. Because not everyone wants them due to their short duration, I have added logic such that it will send the Micro work units only if the Measured Integer Speed is 4294 million ops/second or less. That number was chosen as it equates to that of a Intel E2160 Core 2 Duo running @ 1.8Ghz which is the slowest CPU I currently own but capable of running the Mini Collatz work units. In other words, it was a somewhat random choice and can be easily changed if the consensus is to make it either larger or smaller. The goal is so that those with older slower CPUs can receive Micro Collatz work units and complete them in a reasonable amount of time while keeping faster CPUs crunching for > 30 minutes. So, please let me know if this change causes any problems. 5 May 2014, 0:03:55 UTC · Comment

Missing Apps Part 2
If you have a CPU that cannot complete the mini_collatz work unit in less than 8 hours and would like the option to run the micro_collatz work units on your CPU, please let me know and I can enable the CPU apps for the micro_collatz work units.

I disabled the OpenCL for Intel GPUs for large_collatz work units as a majority of the Intel GPUs would not be able to complete the large work units before the deadline.

The deadline for work units has been increased to 14 days, up from 7. It will only take effect on newly created work units. It will not affect the work units that have already been created so there will be a mixture of them for a while. In the mean time, I have increased the grace period to 7 days so those work units with a 7 day deadline can be submitted up to 7 days late and still be awarded credit.

Running longer work units reduces network bandwidth, database size, and the load on the Collatz server. When the solo app was initially released over a year ago, there was a bonus for running the solo work units. It was not removed when the multi-size logic was added. When multi-size logic was moved last week, that bonus remained in effect for all apps including micro, mini, and large apps. The purpose of the bonus was to encourage everyone to run the largest app their machine could run. I don't want to only give the bonus to fast GPUs that can run the large work units since not everyone has a GPU fast enough to run the large work units. So, rather than remove the bonus from micro, mini, and solo work units, the credit bonus will not be awarded when any work unit is completed in less than 30 minutes. That way, it is both our best interests to run longer running work units. That, and the less I have to worry about the server, the more bass fishing I can get in on the weekends.

There are still a number of multi-sized solo work units mixed in with the new and larger solo work units. Please don't abort them unless they will run in under 30 minutes. The sooner they are completed, the sooner everyone will get the larger ones.
2 May 2014, 15:55:49 UTC · Comment

... more

News is available as an RSS feed   RSS

Copyright © 2014 Jon Sonntag; All rights reserved.