Page 1 of 1

Expanded share insertion capacity

Posted: Tue Jun 12, 2018 2:06 pm
by Steve Sokolowski
Earlier today, Chris expanded our share insertion capacity. The share inserters had been at 100% CPU usage because the number of coins increased with the addition of Tradesatoshi and the fall in the price of the big coins. In addition, more customers suddenly joined after Constance increased our social media presence.

Because there are no spare servers available, the transition required copying virtual machines between servers, which of course was limited by Gigabit ethernet. The website and the share inserters were switched, so that there are now twice as many cores allocated to the share inserters. Chris will order new servers, but the website may suffer in performance until they are installed due to the reduced resources available to it.

He will investigate whether any shares were missed during the switchover and issue share corrections, if necessary, later today.

Re: Expanded share insertion capacity

Posted: Tue Jun 12, 2018 2:31 pm
by djliss
It looks like earnings are potentially lower today than yesterday, i know many factors are involved so could be nothing to do with it.

Re: Expanded share insertion capacity

Posted: Tue Jun 12, 2018 2:38 pm
by Steve Sokolowski
djliss wrote:It looks like earnings are potentially lower today than yesterday, i know many factors are involved so could be nothing to do with it.
I think that there were about 15 minutes of missing shares, so that implies a 1% bonus at the end of the day. But that was necessary in order to make sure the system has sufficient capacity. Chris will make the corrections.

I think that profitability compared to LTC will be higher than yesterday, because there are so many more coins being mined.

Re: Expanded share insertion capacity

Posted: Tue Jun 12, 2018 7:27 pm
by Steve Sokolowski
The release of the new code failed, so we reverted it. The cause of the problem was that while the new code was designed to handle heavy load by inserting huge numbers of shares at once, when one share fails to insert because of some other bug, a huge rollback occurs and sets the system behind by a lot. We need to figure out a way to prevent such huge rollbacks from occurring when a bug affects one out of 20,000 shares.

The problem right now is that there are so many coins running that it takes a lot of CPU power to compute how much each coin contributes to the pool's earnings. The system fell behind, but it is catching back up now and Chris will correct the shares later.

Then, we'll try again to release tomorrow. This release needs to be issued because it will provide for a tenfold capacity increase in share insertion.