We're currently investigating why the database is getting behind. We think we have an idea as to why, but it will require a few hours to fix.
Some charts will be out of date in the meantime. Mining and payouts should not be affected. We apologize for the inconvenience.
Investigating slowdown
Forum rules
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
-
- Posts: 19
- Joined: Wed Sep 02, 2015 3:13 pm
Re: Investigating slowdown
Thanks for all your hard work!
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Investigating slowdown
This issue has been resolved.
For those interested, the problem was that we deleted 160m shares recently in one of our periodic cleanups, but the table had not been VACUUMed. Therefore, there was a huge amount of wasted disk space and it took a long time for the database to figure out where to write the new shares.
By VACUUMing the table, we restored the database to normal operation.
For those interested, the problem was that we deleted 160m shares recently in one of our periodic cleanups, but the table had not been VACUUMed. Therefore, there was a huge amount of wasted disk space and it took a long time for the database to figure out where to write the new shares.
By VACUUMing the table, we restored the database to normal operation.