Bandwidth Limit Exceeded Issue Solved (or at least Answered and somewhat understandable)

in #steemit7 years ago (edited)

Have you seen this pesky little notice before too!?


If you see this message, do not fret (or become angry). Steemd has added a new tracker bar to help you understand what is going on.

If you scroll down a bit, you can also use these numbers to help you:

You can pretend that it's a game and keep refreshing your status bar periodically. I found that my percentage boosted up to a positive number from this negative percentage after only about 5 minutes.

To get a little more clarity, I think this section is extremely helpful from the Steem WhitePaper:

Bandwidth Instead of Micropayment Channels
The solution to the problems with micropayments is in implementing dynamic fractional reserves. Under this model the blockchain will automatically adjust the reserve ratio for the network during times of congestion. The blockchain will set a target utilization that leaves enough headroom for short term surges in demand. Any time the surges are sustained the blockchain reduces the maximum bandwidth-per-share. When a surge is over and there is surplus capacity the blockchain can slowly increase the bandwidth-per-share.

Bandwidth used by an individual user should be measured over a suitably long period of time to allow that user to time-shift their usage. Users tend to login, do many things at once, then logout. This means that their bandwidth over a short period of time may appear much higher than if viewed over a longer period of time. If the time window is stretched too far then the reserve ratio will not adjust fast enough to respond to short-term surges, if the window is too short then clustering usage will have too big of an impact on normal users.

In our estimate it should be sufficient to measure the average weekly bandwidth usage of users. Every time a user signs a transaction, that transaction is factored into their own individual moving average. Any time a user’s moving average exceeds the current network limit their transaction is delayed until their average falls below the limit.



So, there you have it. This was part of the Steemit plan all along. The bandwidth issue is a "good" thing because it implies that we are growing as a platform and community. The reason that some of us are experiencing the bandwidth issue is related to how frequently we post (unless someone can please share an update to this methodology since the WhitePaper?).

LIVE UPDATES: It looks like the issue will be handled in update 0.19.1

_____________________________________________________

Thanks for reading, I hope you have a great day!
_____________________________________________________

If you want to read more, please take a look at some of my other posts:

Sort:  

Thanks! A better error message is definitely needed!

Agreed! If the error message gave you a timer telling you how long you needed to wait (since I'm sure they could figure out how to estimate that based on the fact Steemd can estimate your negative bandwidth percentage), I think everyone would have a stronger sense of calm and comfort when they're unable to post for XX minutes!

Thanks for your comment :)

there are a few active issues for bandwidth in the github repository for steemit - maybe you can make a suggestion in there and see it realised ;)
https://github.com/steemit/steem/issues/1257

So I haven't been active on Steemit for the past hour or so and I came back to negative (- 444.##%) Bandwidth!??

How in the heck does THAT Happen?? Apparently minnows are being THROTTLED BY Steemit!

Coin Marketplace

STEEM 0.16
TRX 0.15
JST 0.030
BTC 59106.19
ETH 2538.36
USDT 1.00
SBD 2.37