Status as of Saturday, September 8, 2018
Posted: Sat Sep 08, 2018 8:50 am
- The upgrades to all servers were completely successful. Chris was able to patch the Spectre vulnerability on all motherboards, which will improve security by preventing bad coin daemons from predicting private keys in memory in other parts of the system. He also installed more RAM, so that our total RAM now stands at 1.05TB, and upgraded CPUs, so that we now have 124 cores total. There were no known issues introduced by the upgrades and that task is now closed.
- Today, I'm going to focus on resolving some division by zero errors in various queries. These errors are preventing expected payouts from being calculated and some miners are unable to view their hashrates because of them. There is probably one day where hashrates were zero for a single algorithm that is causing the issues.
- In addition to resolving some bugs elsewhere in the system, such as by inserting zero values in the "earnings by coin" chart for days that there were no earnings, Constance continues to improve charity mining. There is now a link to the charities' websites available in the "Payout Proportions" when a customer clicks on the "Add coin" button.
- Vance resolved an issue with static difficulties for mining on algorithm-specific ports when the "a=" password argument was not provided. Previously, the "d=" argument was incorrectly ignored and set to the scrypt default difficulty when "a=" was not provided. Now, the correct behavior of assigning the requested difficulty occurs.
- I'll be continuing to investigate ways to automatically monitor things like CPU usage and free disk space and to provide notifications when these things become critical. Hopefully, I'll get to that this week.
- Chris is installing Quark coins and we hope to have Quark available soon. The code for Quark is already running in production, but as always, we are limited more by research into what algorithm coins actually are than by coding.
- The next major improvements, after a period of bugfixes, will be Monero mining and direct exchange payouts. Direct exchange payouts will allow customers to receive any coin offered at a major exchange for payout, even if it doesn't conform to the standard bitcoin API or the ERC20 specification, but the customer will be required to pay the exchange withdrawal fee.
- The next round of maintenance downtime will be to upgrade the database server from Postgres 9 to Postgres 11. We decided to skip version 10 and go right to 11 because of how close to release version 11 is. Postgres 11 includes significant performance improvements in query parallelism that are important for us to take advantage of before the next bubble starts and the system could become overloaded without them.
- Unfortunately, scrypt hashrate declined despite the profitability improvements. We will be commissioning a poll later today requesting customers' feedback on what features of a mining pool are most important to them. While we don't intend on eliminating the increase provided by the scrypt profitability experiment in the near future, the experiment (which increased profitability by so much - over 10% - that if it were important there would have been at least some effect) proved that profitability is not the most important reason for mining with a pool. We want to find out what is.