Status as of Saturday, August 26, 2017

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 Saturday, August 26, 2017

Post by Steve Sokolowski » Sat Aug 26, 2017 7:39 am

Good morning!
  • Chris has been focusing on network issues over the past day. We believe that connectivity issues are responsible for almost all problems with the system at present.
  • So far, he fixed three issues. First, he found that Javapipe was blocking connections to DNS servers other than 8.8.8.8, so when something tried to connect to the backup nameserver, a long delay occurred. By removing the backup nameservers from the configuration, there is no longer a delay before a retry attempt is made to the primary nameserver.
  • Second, he found that since Javapipe doesn't support ipV6, and the nameserver was resolving names to ipV6 addresses, services would try to connect to those addresses and be unable to do so. Chris disabled ipV6 on all servers and now DNS lookups always return ipV4 addresses. That results in fewer connectivity issues on ipV6-primary connections.
  • Third, there was one IP address that was uploading a huge amount of data to the webserver for an unknown reason. He banned that address and added code to prevent that from happening again.
  • He also discovered that Javapipe is having routing issues with its current datacenter, and that they are migrating customers to a new datacenter. They agreed to provide Chris with a second server in the new datacenter before other customers, and this new server has a third-generation processor instead of the first-generation processor the previous servers had. That means that OpenVPN will have a significant increase in performance, and the routing issues should disappear. This new server is not configured yet, however, because Chris will need more time this morning to finish the task. He expects to finish setup by tomorrow, and then transition to the new server. Chris's troubleshooting last night was responsible for a few server restarts.
  • On the WAMP side, there are two fixes on which I am focusing. First, I'm creating additional "realms" so that CPU usage for WAMP can be distributed across more cores. Second, I'm going to resurrect the code for the "difference engine," which will reduce bandwidth usage for WAMP by a factor of 10. I hope to complete both of these fixes by the end of the weekend. TransportLost() exceptions have been causing unknown effects on profit recording.
  • Once the WAMP issues are resolved, and the connectivity issues are fixed, then we will reevaluate and see whether share issues are still occurring and take further action there. At present, we can't perform a true investigation of the other issues because we need to rule out that disconnects are responsible for them.
  • Chris completed the spreadsheet evaluation of future plans, but I still have to review it. I plan to do that next week after we get the connectivity issues fixed and WAMP resolved.
  • To reduce confusion about the evaluation process, I created a FAQ and plan to post it later today. Tickets asking about future plans for the system will be directed to the FAQ. The FAQ might also be of interest to people here, as it will aggregate information into one location.
Sunegg
Posts: 17
Joined: Fri Jun 02, 2017 6:22 am

Re: Status as of Saturday, August 26, 2017

Post by Sunegg » Sat Aug 26, 2017 7:49 am

Thanks for the update Steve!
miles888
Posts: 5
Joined: Tue Aug 22, 2017 4:46 am

Re: Status as of Saturday, August 26, 2017

Post by miles888 » Sat Aug 26, 2017 7:50 am

Good to hear! Thanks for the update!
lightstockchart
Posts: 3
Joined: Thu Aug 24, 2017 8:25 pm

Re: Status as of Saturday, August 26, 2017

Post by lightstockchart » Sat Aug 26, 2017 11:16 am

Thanks Steve.
coastalminer
Posts: 8
Joined: Mon Aug 14, 2017 9:31 pm

Re: Status as of Saturday, August 26, 2017

Post by coastalminer » Sat Aug 26, 2017 12:10 pm

Good to hear.. What's WAMP?
mycide
Posts: 174
Joined: Sun Aug 06, 2017 7:44 am

Re: Status as of Saturday, August 26, 2017

Post by mycide » Sat Aug 26, 2017 1:29 pm

Thank you for your efforts!
Running rigs: KNC Titan, Antminer D3 & L3+'s
jwchong
Posts: 4
Joined: Sat Aug 26, 2017 12:49 pm

Re: Status as of Saturday, August 26, 2017

Post by jwchong » Sat Aug 26, 2017 2:36 pm

Thanks for the update. Hope that the 4.99% fee that we are paying really can get the quality that you have mentioned in FAQ to justify what we are paying. Too much downtime and connection issue does not justify the higher fee that we are paying compared to other multi pool or nicehash. Please keep your promise. Thanks
Locked