The following is copied from Discord NKNx channel, by NKNx developer ChrisT:
ChrisT | nknx — Today at 8:14 AM
Hey @everyone, I think you already recognized on the chat but if not be aware that current updating-processes (nodes and wallets) on NKNx are stopped until further announcements. That brings me to both of the problems we currently see with NKNx:
The performance of the NKNx portal itself within the last weeks/months.
As many of you know: the overall performance of NKNx is just bad. This is not because it has too many visitors, it is because it’s built-in node- and wallet updating function. For those who don’t know: NKNx establishes a connection to all of the nodes you store in the database (currently more than 60k) to get their status and save it to the database. If you do some math and assume that every node update will just take 0.5sec (contacting the node, await response, write to database) you will come to the conclusion that updating 60k nodes will take around 8 hours. Of course we already run the node updater in something called multithreaded mode but that leads to an overall poor performance of nginx and PHP itself.
The “donation” on each fastDeploy node
One and a half year ago we decided to introduced the “forced donation” feature on fastDeploy. This decision was mainly powered because of the fact that we won’t be able to pay server costs just by begging for donations. At this time the NKN token was valued at 3ct, so not a big deal for most of the miners. Now after the price hit 60ct+ it is a big deal for many small miners and doesn’t feel like the best solution for future services.
How to solve both problems?
Currently we’re thinking about converting NKNx to a SaaS platform. Meaning: every user is generally capped by the numbers of nodes/wallets he can watch through NKNx. Also the number of FastDeploys is limited. That gives small miners the opportunity to play around with NKN and get to know the project easily.
For the more heavy users we plan to establish different subscription tiers that enable higher limits and additional features like eMail notifications and the direct API-deployments for DigitalOcean, Google Cloud, Hetzner, etc. Also the smaller tiers won’t be able to see history data since their nodes won’t be updated by the server anymore.
But now I need your opinion! What do you think NKNx should become? Is our idea and the problems understandable for you? As always every message is appreciated!