Status as of Monday, June 22

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.
Locked
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Status as of Monday, June 22

Post by Steve Sokolowski » Mon Jun 22, 2015 9:26 am

Here's today's status:
  • On Saturday morning, I resolved some mining server issues, and the changes appear to have been successful. One point I realized is that even though an issue might not occur very often, it's possible that the reason it occurs infrequently is because people who encounter it don't use the system. Therefore, it's important to fix issues that seem to affect very few people.
  • I spent a lot of the day on Saturday and Sunday improving performance.
  • Chris was successful in moving over most of the daemons to these new servers. Of the remaining daemons, 5 are unable to be compiled or (like litedogecoin) do not have official repositories, 35 are downloading blocks and will be moved tonight, and 9 are Comkort-only coins that will be discontinued.
  • Most of the Comkort-only coins have already gone into error because their market depth is too shallow. To continue to reduce server load, Chris will likely be discontinuing those coins earlier than the original June 29 deadline.
  • The 2-minute restarts that occurred three times yesterday were each to move about 20 daemons to the new servers. Two more of those restarts may be needed over the next week.
  • Cryptsy continues to cause us problems by not promptly responding to withdrawal requests. Today, payouts for 4 coins failed due to this problem. Since we withdrew about 50 coins from Cryptsy, an 8% failure rate is not acceptable. Chris is working on this issue.
  • We still have not completed indexing of the block explorer because we need all the daemons moved to the new servers first. Once we have done that, we can then assign the database server more memory and not interfere with other queries.
  • There were some blocking database calls in the mining server that I resolved. Now, when the database is overloaded, the mining server will queue shares for 4000 seconds and try to write them to disk when the disks become available.
  • I completed and tested ccex, and we will begin trading there if they can remove the rate limit. They have a rate limit that prevents trading more frequently than every 5 seconds. To see why that's a problem, consider if we need to get prices for 100 coins there. That means it would take almost 10 minutes to make the trades. At Poloniex, we issue 100 trades in less than five seconds. Ccex is not the only exchange to artificially limit its trades in this manner, and I don't understand why they or any other exchange, which makes money from trades, would want to place any barriers in the way of customers making them more money.
Locked