Status as of Thursday, September 24

[Steve Sokolowski]

A few brief thoughts:

• We were able to eliminate another four queries from the share insert procedure, reducing the time to insert a share to 1.32ms from 1.49ms. As a comparison, the number was at 2.00ms per share on Saturday, and was at 1.21s in October 2013. We'd like to get this down to 900us or 800us by this weekend by reducing the number of triggers that need to fire when a share is inserted. We also have an idea as to how to parallelize this without waiting for Postgres 9.5 which, if possible, should allow us to increase capacity by a factor of 6.
• The goal of these improvements is to reduce the frequency and the length of time when it does happen of the database getting behind. Chris believes that some customers leave when their stats aren't fully up to date.
• Since it's the end of the month, I'll have four days this weekend with which to work on the project. After finishing up the performance improvements, I'll investigate improving the API, which is a simple task that was requested by a customer. Then, I'll add more checks to deal with additional situations where coins are not sold or transferred to exchanges. Finally, I'll see what can be done about the "mobile interface" issues. Unfortunately, I've already implemented all the things except for one that tuscondirect suggested, so the solution will be more complicated.