RE: 🔊BitShares Hangout #58 | 2018-2-10 | Sat @200PM UTC | OpenSource Agenda [Beyondbit Raffle Powered by SP!]
👍 Another great Bitshares discussion in the books. I am happy to see the participation and guest interactions grow each week. Thank you @fox, @Taconator and @dahaz159 for the topics of discussion and @SteemPower for the weekly State of the Network report. Thank you @ash (Fav) for moderating and recording the event each week. I'm happy to see everyone starting to use the topic slides I create in their posts and updates.
You are all appreciated!!!
💬 Great discussions initiated by @fox on establishing a BitShares Core Team for future development efforts. Aside from the technical advancements to the platform, this would greatly help in the long term marketing and public relation efforts to bring the Bitshares DEX and assets to the mainstream crypto-trading ecosystem. Hopefully this topic can stay at the forefront in the coming weeks.
⛔ There is an issue that needs to be discussed among those with the technical background to provide answers to it. In recent days many of us have been experiencing multiple failed transactions on the DEX as the daily transaction volume has increased. Each time I get a failure notice I check Blocktivity.info to see where the transaction rate is at. Just to note, I have never had a failed transaction on days under 1,000,000 mark.
We see Bitshares doing it's thing on the technical side, not even breaking 0.1% capacity for handling the transactions, even though we are now experiencing an increase in failures to complete them.
Are there issues with nodes, does the base-level server requirements for running a node need to be increased (like they did recently on STEEM) to handle the increase in average daily transactions?
If approved from my topic list it will be discussed. This network has much greater capacity than what is showing in real-time, and It's about time to explore that capacity in a proper way.
Much appreciated.
We spend A LOT of time over on the Whaleshares Discord onboarding new people to the Bitshares DEX and teaching them how to use it with Fuzzy's cross-chain tokens, so when these issues of failed transactions come up after preaching 3-10s confirmations while running at 0.08% capacity - we have a hard time explaining it away.
Thanks for the excellent visual slides
The throughput that is listed at blocktivity is the actual throughput of processed operations through each of the nodes. In contrast, your wallet/client interacts with one API node that is performing additional work besides the processing of operations such as providing data to clients and receiving new operations that are submitted by clients. Specific API nodes can become overwhelmed by this additional work however it is not an issue that affects the actual processing of operations.
It is similar to an outer network ring that is connected to an inner network ring, and your computer is connected to the outer ring. If the entire outer ring is slow, it does not matter how fast the inner ring is. Fortunately, the entire outer ring is not slow. It is a matter of finding a fast connection point on the outer ring.
Thank you for the explanation. Following up on that then, is there anything the average user can do to avoid this issue? Can we set/change the nodes we connect to through Bitshares/OL wallets, or is that not in our control at all?
For those who are more technically inclined and roll with it, it's an inconvenience but not a big deal. For the new people in Whaleshares we bring on to the DEX they get frustrated to the point of giving up and we try to explain it away with internet/bandwitdh/is-what-it-is type answers.
Yes, within the GUI wallet look for Settings:Access and then select a different API node