Page 1 of 1

Status as of Tuesday, June 2

Posted: Tue Jun 02, 2015 9:45 am
by Steve Sokolowski
Here's today's status, after a long weekend of development:
  • Our block explorer continues to churn away at indexing. We had to spend a day modifying the database because we discovered that the full index of all chains would require over 3TB. While we have the disk space, we don't have enough bandwidth to back up all that data. We were able to make some optimizations to get the daemons to index faster and use less space. It looks like about 10 daemons are fully indexed now. At first, there will be some coins that don't display any data on the block explorer (there is no error programmed in that for performance reasons), but that should be fixed as more coins are indexed. We expect the indexing to continue for up to 20 more days.
  • Unfortunately, Chris can't find the time to do anything with the two new servers that are sitting idle; if he could, we could add more coins and make the indexing proceed faster.
  • Chris's time is being taken up almost entirely by resolving daily issues that occur with the system. For example, it cost over six hours yesterday because there was a buy order for one satoshi at an exchange that caused a pricing error. Since everything that can go wrong will eventually go wrong, once we fix that problem there will probably be something else that comes up. The goal is for 100% automation of these sort of problems so that development can again proceed, so we are going to devote this month to putting code in place to save Chris time that can instead be diverted to other, more useful, tasks.
  • A website update today will move the "recent shares" table on the earnings page down to the bottom, at the suggestion of Kires.

Re: Status as of Tuesday, June 2

Posted: Tue Jun 02, 2015 10:05 am
by dexubdg
There is a truble with connection to your pool :( @ 02.06.2015.

Re: Status as of Tuesday, June 2

Posted: Tue Jun 02, 2015 10:43 am
by Steve Sokolowski
These disconnects appear to have been happening all night. Unfortunately, it looks like the same problem with disconnects that was present for a month has returned.

Chris will look into this issue and get back to you as soon as he can.