SteemDB.com - Migration complete and a few thoughts on it is future.

Nicely, it took longer than I expected, however SteemDB.com is slowly coming back to lifestyles.

The statistics migration I began a pair days in the past completed in advance these days and i'm bringing the services again online. if you nevertheless see the "DB Migration" message still (on every web page), your DNS has no longer up to date to the new server. The DNS ought to update within the coming hours and the website will then come to be available over again.

if you're very impatient, you could usually get entry to the website online via it's IP address: http://144.76.176.150

New Server
the brand new server SteemDB is hosted on is now furnished by means of @privex, and i've had first-rate support from @someguy123 getting this all setup.

SteemDB went from a 96gb RAM server with 8 cores to a 256gb RAM server with 12 cores. i have optimized and upgraded all the software to the modern-day versions, configured the filesystem for excessive IO throughput, and have to have masses of room to develop over the following yr or so.

modern-day issues and standing
some notes approximately this new deployment and problems surrounding the migration:

The database sync is currently catching up, as I write this it became processing block 18636474 (2018-01-02). So currently the 9 most current days of facts are lacking from some sections. This new server is processing those blocks at a price of approximately 3-6 blocks/2d. we are currently at a top of 18892572, this means that there's approximately 250k blocks that want to be processed. At a rate of 3 blocks in keeping with 2nd (to be conservative), it'll trap as much as the modern-day block peak and finish processing in about 24 hours.
The witness pages and other sources that pull facts live are unaffected by using the sync method, but pages like an accounts transfers/votes will be impacted through the sync.
The account records module is disabled for the next 24 hours, so no new snapshots of debts may be created until the sync is finished.
The apps page is missing facts and fairly broken, and i will look into what's taking place here. it is maximum possibly because of the inactive records module, which additionally creates snapshots of app utilization.
The homepage is now not cached, so it is somewhat slow. i'll work on caching this once more within the destiny.
Any overlooked blocks via witnesses for the duration of this migration have been now not recorded alas.
wherein SteemDB is going from here
over the past month i have been doing loads of considering the numerous projects I maintain regarding the Steem environment, and one reoccurring concept i've is that i've too many lively projects. i'm still in the planning phases, but certainly one of my goals in 2018 is to shed or offload some of this workload so i can cognizance on the tasks that virtually count number to me, as well as the surroundings as an entire.

With that being said, SteemDB isn't always one of the tasks that I need to individually forestall preserving. For months now in informal conversations i have stated that I really want to rebuild SteemDB and create a v2 of my block explorer code, and i am hoping to find the time to accomplish that this 12 months. SteemDB was my 2d Steem associated undertaking (created Aug 2016) and i have found out a lot considering that it's introduction.

In 2018, i would very similar to to make an effort to take a seat down and rebuild SteemDB into some thing higher. improve the technology, the scalability, it is responsiveness, and usability. these foundational equipment (wallets, blockexplorers, and so on) are crucial to on-boarding new users and developers alike, at the same time as providing outside transparency into the operations happening at the blockchain.

fortuitously, this new server has room to develop, and i will match a v2 right along v1 until it's prepared to update it :).