What is the use of CPU exceeding the standard?
Today, many EOS users mention that their CPU resources are out of standard (in some EOS browsers, such as eosflare, they are shown in red), making transfer operations impossible.
Let's talk about what's going on. Let's take a look at several questions about the EOS resource model. This article is only based on my limited personal understanding, if there is any misunderstanding, I look forward to your correction.
Today we only talk about CPU, because the current network resources are not scarce, only a very small amount of EOS can get enough bandwidth resources.
What is CPU resources "explosion red"?
If the amount of CPU resources you use in your account exceeds the total amount of CPU allocated to you. So, in some EOS browsers, if it's too much, it's shown in red, which we call CPU pop-up.
Take EOSFlare as an example, and if it is not large enough, it will still be yellow.
When will this happen?
When the number of EOS used as collateral for CPU resources suddenly increases in an EOS network, the available CPU resources corresponding to an EOS will be reduced.
For example, 10,000 EOS mortgages in your account were used in exchange for CPU resources, which were originally available for 10 minutes of CPU computing.
You've been playing games for a long time. Look, CPU resources have been used up for a minute, and there are still two minutes left. Don't rush to increase collateral. Keep playing.
Suddenly, a DAPP team mortgaged a large number of EOSs, for example, doubling the total amount of mortgage directly, which resulted in halving the amount of CPU resources available for each EOS.
Then, the CPU resources corresponding to your 10 thousand EOS become 5 minutes.
In this case, you've spent eight minutes of CPU resources; the amount of CPU resources allocated to your EOS has halved because of the surge in mortgages, and the total amount has changed to five minutes.
In this case, the overuse of your CPU can lead to no more transactions. At this time, your available CPU time is negative.
Because the available time = total quota time has been used.
Now, how can we solve this problem?
Two ways:
First, increase the total quota, that is, more EOS can be obtained by mortgage more CPU. According to our assumption above, you need to re-mortgage at least 10,000 EOSs to get the total CPU resource quota to change to 10 minutes.
The second is waiting. Because the CPU resource is linear recovery, and it will fully recover in 4 hours.
In addition, if the mortgage volume of the main network decreases, it means that the CPU resources allocated by a single EOS will increase and the total quota will also increase.
How to improve: discuss together
The above is only the current solution, but either, more tokens need to be mortgaged or, well, longer. For EOS users, experience is not good. How to improve it better?
Just now, in Chintai's project discussion group, some friends have provided some very interesting solutions. CPU resource model, how to optimize, reduce the impact on users, how to face today's scenarios, so that more people do not have to face the same problem.
What is a better resource allocation system? I haven't thought of it yet, and I'm looking forward to my friends who are more concerned.
Support:[http://www.bitaves.com/]