Status as of Tuesday, June 23

Discussion of development releases of Prohashing / Requests for features
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.

While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Post Reply
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Status as of Tuesday, June 23

Post by Steve Sokolowski » Tue Jun 23, 2015 9:01 am

A brief update of status:
  • Last night, Chris permanently disabled Comkort and discontinued all their coins. There were no payout coins owed, probably because those coins had been in error due to shallow markets for some time.
  • There are 22 remaining daemons to move, so Chris is getting to the end. It appears that system performance will be acceptable once all the daemons are removed.
  • We were already able to restart block explorer indexing, albeit at a single-threaded rate.
  • I resolved a problem where people trying to authorize before subscribing to mining jobs would, on occasion, receive a rejection. This issue only happened once yesterday, but if it always happened to the same person, fixing it will allow that person to connect.
  • As detalied in the "support" forum, there was an issue discovered that would cause the "hashrate" charts to be off, both personally and on the overall charts page. The payouts would be normal regardless of what the hashrate chart showed. The cause of the problem was that sometimes, system load would cause shares to back up for writing, but before they were written, the hashrate calculation routine would run, producing numbers that appear to be lower. The shares would later be inserted, and if the hashrate calculation routine had been run again (which it would not), the computed hashrate would then be higher. This issue is now fixed.
  • We anticipate one more restart once the remainder of the daemons are moved between servers. At that time, we will also restart the database, in order to reallocate 48GB of memory to the database that was previously used by daemons.
Post Reply