Status as of Thursday, November 23, 2017

[Steve Sokolowski]

Happy Thanksgiving!

• Chris successfully moved all the servers to the new rack and installed the new processors, memory, and servers. He also put in another eight solid state disks, for a total of 30. There are now seven servers, and we have spare capacity of about 40 cores and 128GB of RAM. This capacity will be enough to host parallel mining servers and SHA-256 mining, as well as to deal with the immense and growing size of the ETH blockchain.
• Some customers are reporting connectivity issues this morning. Chris will investigate the connection limit when he awakens and increase it to resolve those issues.
• There will be no share corrections for yesterday's maintenance, because the system was offline and no recording occurs occurred.
• A brief reminder: payouts are promised to occur some time during the next day after balances mature. Please hold off on submitting support tickets or forum posts until the full day has passed. We do not guarantee a specific payout time because, especially on unreliable networks like bitcoin, it can take a very long time for us to confirm all the money we need to pay customer debts. By submitting tickets before 24 hours has passed, customers take away time from Chris, who could instead be optimizing the system and implementing new features.
• We expect to have a few more periods of downtime in the coming weeks. We still need to upgrade to Postgres 10 before we can go with the parallel mining release, because Postgres 10 has parallelism improvements itself. We also need to release an intermediate mining server upgrade to support Livecoin, because Novaexchange is going offline soon.
• We also have some great news. It turns out that "turbo mode" was disabled on the mining server, slowing its performance by at least 10%. We'll be able to increase the number of connections by 10% later today once Chris gets up solely because he modified this BIOS setting.
• I'm ahead of schedule on the mining parallelism. It's feasible we may be able to enter testing with that as early as next week.

[AppleMiner]

I am guessing by "TURBO MODE" you mean Chris DISABLED the thermal throttling features of the intel cores in the BIOS so it no longer downclocks the speeds when it either gets too hot or isn't working to max capacity so it always drives the CPUs at 100% power.

Or did the motherboard have an auto-overclock mode?

[Aura89]

I am guessing by "TURBO MODE" you mean Chris DISABLED the thermal throttling features of the intel cores in the BIOS so it no longer downclocks the speeds when it either gets too hot or isn't working to max capacity so it always drives the CPUs at 100% power.

Or did the motherboard have an auto-overclock mode?

He might be referring to Intel Turbo Boost, which is something that is able to (but is generally not defaulted to) turn off.



Like that, but for the server processor.

[Steve Sokolowski]

I am guessing by "TURBO MODE" you mean Chris DISABLED the thermal throttling features of the intel cores in the BIOS so it no longer downclocks the speeds when it either gets too hot or isn't working to max capacity so it always drives the CPUs at 100% power.

Or did the motherboard have an auto-overclock mode?

He might be referring to Intel Turbo Boost, which is something that is able to (but is generally not defaulted to) turn off.



Like that, but for the server processor.

Yep, that's right.