RE: 🔊BitShares Hangout #58 | 2018-2-10 | Sat @200PM UTC | OpenSource Agenda [Beyondbit Raffle Powered by SP!]
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