create account

Dan Larimer explains how REX will solve the current CPU issue by littleboy

View this thread on: hive.blogpeakd.comecency.com
· @littleboy ·
$173.37
Dan Larimer explains how REX will solve the current CPU issue
A while ago EOSGo [shared](https://www.reddit.com/r/eos/comments/9v8u0o/dan_larimer_on_cpu_issue/) the following news update in the r/eos subreddit about CPU shortage. It’s a screenshot from telegram which shows Block.One CTO, Dan Larimer explain how resource exchange will solve the CPU scarcity problem of EOS mainnet. Here’s the update: 

![eos update.png](https://ipfs.busy.org/ipfs/QmYmftpj5SgGGUo9EXqGgCR1cUPR5xEBZ9PnD311h1YEH3)

EOS has been facing some serious CPU issues which are limiting the network usage. The EOS.IO code states in its config file that it is targeting 1000 tps. But in reality, it hasn’t been able to reach that level with a certain degree of stability. Occasionally it fires up to 3000 tps but that doesn’t stay for long. Recently, a research article criticized EOS for not reaching tps goals.

The comments Dan made were somewhat of a response to those concerns. He explained why EOS wasn’t reaching high tps. Since EOS CPU resources are awarded linearly, those with a lot of tokens get lot of CPU which they generally don’t use. This is why the network has a low % CPU utilization but still hits 100% since those who are transecting have only 5% of the staked tokens.

Which means the other 95% CPU resources are not being utilized since they are awarded to users who aren’t transacting. After REX is launched, the users who have unused CPU resource, that is, those EOS holders who have a lot of tokens but aren’t transacting will be able to sell their CPU resources. So, all of those unused CPU resources will enter a free market and will be used.

That will solve the CPU scarcity problem and increase the tps (by at least 5 times). One last thing:

In the original reddit thread where it was posted, a user asked who will consume CPU resources and from where demand for CPU resources will come. The demand to use CPU will come from users who have run out of CPU resources and need more to do more transactions. Let me explain this with an example.

Lets assume that I have 4 EOS staked for CPU on my account. I made 100 transfers today which depleted all the CPU time allocated to me. Now I need to do some more transactions. I can solve this by staking more EOS or renting CPU time from REX. Renting from REX is lot cheaper than staking more EOS. So, what I will do is buy some CPU time from someone else and use that to transact. This is how demand for CPU time is created.

Thanks for reading, if you have any questions about REX, feel free to ask me in the comments. If you liked the article, please consider sharing it in your facebook / twitter timeline.
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 709 others
properties (23)
authorlittleboy
permlinkdan-larimer-explains-how-rex-will-solve-the-current-cpu-issue
categoryeos
json_metadata{"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["eos","cryptocurrency","crypto","blog","busy"],"users":[],"links":["https://www.reddit.com/r/eos/comments/9v8u0o/dan_larimer_on_cpu_issue/"],"image":["https://ipfs.busy.org/ipfs/QmYmftpj5SgGGUo9EXqGgCR1cUPR5xEBZ9PnD311h1YEH3"]}
created2018-11-09 07:15:36
last_update2018-11-09 07:15:36
depth0
children2
last_payout2018-11-16 07:15:36
cashout_time1969-12-31 23:59:59
total_payout_value131.336 HBD
curator_payout_value42.032 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,595
author_reputation205,792,878,086,848
root_title"Dan Larimer explains how REX will solve the current CPU issue"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id74,960,800
net_rshares171,170,348,505,664
author_curate_reward""
vote details (773)
@conceptskip ·
Thats an interessting dynamic, really curious how this will play out when rex is there
properties (22)
authorconceptskip
permlinkre-littleboy-dan-larimer-explains-how-rex-will-solve-the-current-cpu-issue-20181109t214659220z
categoryeos
json_metadata{"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["eos"],"users":[],"links":[],"image":[]}
created2018-11-09 21:47:03
last_update2018-11-09 21:47:03
depth1
children0
last_payout2018-11-16 21:47:03
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length86
author_reputation3,288,745,933,815
root_title"Dan Larimer explains how REX will solve the current CPU issue"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id74,999,306
net_rshares0
@steem-ua ·
#### Hi @littleboy!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your **UA** account score is currently 4.111 which ranks you at **#3213** across all Steem accounts.
Your rank has dropped 4 places in the last three days (old rank 3209).

In our last Algorithmic Curation Round, consisting of 260 contributions, your post is ranked at **#186**.
##### Evaluation of your UA score:

* Some people are already following you, keep going!
* You have already convinced some users to vote for your post, keep trying!
* Try to work on user engagement: the more people that interact with you via the comments, the higher your UA score!


**Feel free to join our [@steem-ua Discord server](https://discord.gg/KpBNYGz)**
properties (22)
authorsteem-ua
permlinkre-dan-larimer-explains-how-rex-will-solve-the-current-cpu-issue-20181110t084808z
categoryeos
json_metadata"{"app": "beem/0.20.9"}"
created2018-11-10 08:48:09
last_update2018-11-10 08:48:09
depth1
children0
last_payout2018-11-17 08:48:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length767
author_reputation23,214,230,978,060
root_title"Dan Larimer explains how REX will solve the current CPU issue"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id75,022,556
net_rshares0