Measuring RC costs for 0.20.6

in #steemdev6 years ago (edited)

A new bugfix release of steem (0.20.6) is currently prepared for release next week. @reggaemuffin already merged the most important changes into his live test environment https://testbed.reggaemuffin.me/ (more infos.

I will do some tests regarding the changed RC costs:
The broadcasted operation can be seen https://steemd.com/@beembot
image.png

RC costs measurements

Version 0.20.5 was measured on https://api.steemit.com. 0.20.6 was measured on https://testbed.reggaemuffin.me/.

The RC costs were measured by:
For 0.20.6 (https://testbed.reggaemuffin.me/)

        node = "https://testbed.reggaemuffin.me/"
        stm = Steem(node=node, keys=[wif_posting])
        account = Account("beembot", steem_instance=stm)        
        rc_mana_old = account.get_rc_manabar()
        print(account.steem)
        # place for broadcast a operation      
        sleep(5)
        rc_mana_new = account.get_rc_manabar()
        rc_costs = rc_mana_old["current_mana"] - rc_mana_new["current_mana"]
        print("RC costs: %f G RC" % (rc_costs / 1e9))

For 0.20.5 (https://api.steemit.com):

        stm2 = Steem(node = "https://api.steemit.com", keys=[wif_posting])
        account = Account("beembot", steem_instance=stm2)
        rc_mana_old = account.get_rc_manabar()
        print(account.steem)
        # place for broadcast a operation      
        sleep(5)
        rc_mana_new = account.get_rc_manabar()
        rc_costs  = rc_mana_old["current_mana"] - rc_mana_new["current_mana"]
        print("Costs: %f G RC" % (rc_costs / 1e9))   

Measurements

Transfer

versionRC costs [G RC]
0.20.60.300629
0.20.50.254544

Vote

versionRC costs [G RC]
0.20.60.115230
0.20.50.288244

Custom_json (follow)

versionRC costs [G RC]
0.20.60.404449
0.20.50.070962

Custom_json (reblog)

versionRC costs [G RC]
0.20.60.106790
0.20.50.092349

Comment

versionRC costs [G RC]
0.20.61.966627
0.20.51.821318

Conclusion

RC costs for a vote and a follow custom_json operation will be changing. RC costs for a vote are reduced by a factor of 2.5. RC costs for a follow custom_json OP are increased by a factor of 5.6. The RC costs of other custom_json operation is not affected.

The RC costs of all broadcasted operations are slightly increased, as now the execution time is now included in the RC cost calculation.

Link to the commits:

There are three changes related to RC costs:

Sort:  

Oh... will make it even more difficult for noobies. Not good!

.

There are three changes:

.

A follow op is costly, as it has to be collected and stored into a database. The number of follower influences for example the feed. When all steemit user would follow 100000 accounts, the performance would be decreasing I think. All other custom_json are not that costly, e.g. a custom_json for steemmonsters do not influence the performance, as they will not be parsed by a steem API.

Does it mean that I should follow now ASAP as many as I can of those whose content interests me?

flagged for bid bot abuse @steemflagrewards

Steem Flag Rewards mention comment has been approved! Thank you for reporting this abuse, @themarkymark.

  • bid bot abuse
    You bought votes to increase the rewards of your post above the value of its content. This post was submitted via our Discord Community channel. Check us out on the following link!
    SFR Discord

Yes, if you want to save RCs, then you should follow everyone you intend to before the update.

You got a 100.00% upvote from @luckyvotes courtesy of @stimialiti!

This comment has received a 55.56 % upvote from @steemdiffuser thanks to: @stimialiti.

Bids above 0.05 SBD may get additional upvotes from our trail members.

Get Upvotes, Join Our Trail, or Delegate Some SP

You got a 31.25% upvote from @sleeplesswhale courtesy of @stimialiti!

Hi holger80 !

Do you know Share2Steem ?
It's a new application that allows you to automatically post on Steemit what you publish on Instagram, Twitter or Youtube.
This way you can build your community here on Steemit and on your traditional social media at the same time, and with no extra efforts !

For the latest news about the Share2Steem application, visit our @share2steem profile.

See you soon on https://www.share2steem.com

This message is generated automatically and only once per user. We won't bother you again.

Thanx to inform about this. I was already surprised because I can do nothing after very little activity, because of lack of RC.

Thanks for testing and for sharing the findings!

These changes are importent. Thank's a lot for sharing them. Hope that they don't have much influence to my activities here at STEEMIT.

Posted using Partiko Android

Great job, thank for this information, my bro @holger80

Hi @holger80!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 7.006 which ranks you at #84 across all Steem accounts.
Your rank has not changed in the last three days.

In our last Algorithmic Curation Round, consisting of 391 contributions, your post is ranked at #20.

Evaluation of your UA score:
  • Your follower network is great!
  • The readers appreciate your great work!
  • Good user engagement!

Feel free to join our @steem-ua Discord server

This is very informative.

Did you get to test / understand the following : https://github.com/steemit/steem/releases/tag/v0.20.6rc1

Removed the old bandwidth system. This includes the removal of several API fields that were specific to bandwidth and the removal of the witness_api, which was used exclusively for returning information related to bandwidth. (#2039)

This means that the witness_api is removed. The old bandwidth system was replaced by the RC system. By removing the old bandwidth system, the blockchain reply time is reduced.

Yea - there was a typo. The correct issue is #3029 it was mentioned 2039 earlier :-D

https://github.com/steemit/steem/issues/3029

Aggggh the pain.
thank @holger80

Hey, @holger80.

I guess I'm looking at the changes and thinking that voting will be cheaper, but everything else will have either a slight or significant increase. Do you know if this is going to be an ongoing thing, incremental changes in the cost of actions until things more or less settle down?

Also, what time next week is this supposed to happen?

Have the cost for claiming an account change? I was able to claim one the first week but have not since because of an increase in RC cost.