BitShares Forum
Main => General Discussion => Topic started by: cylonmaker2053 on March 09, 2016, 01:27:12 am
-
We've come a long way with the technology and have an awesome platform, but the openledger interface still takes way too long to trade. i'm trying to rearrange my open positions to react to changing market prices, and it's taking me, on average, about 30-60 seconds to execute each trade. that's from when i click either Buy, Sell, or Cancel ...it takes sometimes that long just for the confirmation window to pop up, and far too often trades expire unexecuted bc it took too long.
There are a variety of interesting new feature proposals floating around the community for debate, but compared to any of those the relative value of continuing to tighten up and improve the DEX experience should be priority #1.
For starters, does anyone know why we're having such variability in interface latency? Sometimes it works fairly quickly (but should still be constantly improved), but times like this are so frustrating when i'm trying to place a few dozen orders at once. it shouldn't take me 30 minutes to get in my trades.
-
A workaround:
Try a different API connection server. If this is still too slow, run your own node.
-
Not sure why you're having issues but I would guess it's related to your internet connection. There's a fix coming up that enables compression of the websocket data from the witness_node which might help.
There's also a huge bug that causes the witness_node to send out useless unchanged objects on every block but no one seems interested in taking that on. @abit think you could handle that one?
-
@cylonmaker2053 Yeah I had some delays before as well and assumed it was my computer/connection. Can you test trading a little bit on: https://bts.bitcash.org and let me know if you experience the same lag? It's our faucet wallet. Thanks!
-
A workaround:
Try a different API connection server. If this is still too slow, run your own node.
yeah, i've tinkered with switching API connection; sometimes it works, other times it doesn't. Still, improving these kinds of performance issues should be the #1 priority, especially as we get new traders to experiment with the DEX.
-
Not sure why you're having issues but I would guess it's related to your internet connection. There's a fix coming up that enables compression of the websocket data from the witness_node which might help.
There's also a huge bug that causes the witness_node to send out useless unchanged objects on every block but no one seems interested in taking that on. @abit think you could handle that one?
sounds like that's a great project to tackle. Anything that improves the user experience is a great idea.
sometimes i have these issues when at a cafe with slow wifi and i'm connecting through a VPN, but what happened last night was while at home with very good connection.
-
@cylonmaker2053 Yeah I had some delays before as well and assumed it was my computer/connection. Can you test trading a little bit on: https://bts.bitcash.org and let me know if you experience the same lag? It's our faucet wallet. Thanks!
cool i'll check it out later today when i have more time. thanks...
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
-
For me is about 5 sec from Tx click to have the confirmation windows, click it and have it confirmed.
I running the light client, maybe it's fatser ?
-
i have no problems today!
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
Tried to change the Api Connection in the settings?
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
Imo as a market maker, you should use your own witness_node. :P
Good news is that bug mentioned above is solved yesterday, so the speed will be improved after next hard fork.
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
Tried to change the Api Connection in the settings?
yes sir, that's usually the first thing i do; still, i'm thinking about the impression that'd be made on new users to the trading platform. sometimes the API swap works, other times it's still slow.
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
Imo as a market maker, you should use your own witness_node. :P
Good news is that bug mentioned above is solved yesterday, so the speed will be improved after next hard fork.
excellent! looking forward to the increased speed. trying to improve technical performance should be a never ending goal.
eh, you're probably right, i should run my own witness node, but i'm a little lazy with the tech stuff and just like to trade and crunch numbers :)
-
in case anyone's wondering why there's practically no order book in the BTC-BTS market, i haven't been able to place a single trade for the last 15 minutes; now i'm giving up for the evening and heading out. same for SILVER; i had a half dozen trades execute, but now i can't re-load new ones with these issues.
(https://cdn.pbrd.co/images/2aKRccH2.png)
-
I agree , the dex speed should be improved.
I can not place orders or send bts on windows lite wallet. It is so slow!
-
in case anyone's wondering why there's practically no order book in the BTC-BTS market, i haven't been able to place a single trade for the last 15 minutes; now i'm giving up for the evening and heading out. same for SILVER; i had a half dozen trades execute, but now i can't re-load new ones with these issues.
(https://cdn.pbrd.co/images/2aKRccH2.png)
I have the same problem for the last several hours.
-
ugh yeah i'm having the hardest time trying to get in a last bunch of orders for the night. it's taking me way too long to do this, far too many timed out orders.
-
(https://cdn.pbrd.co/images/2aXFxMtW.png)
-
I have experienced some of these performance issues as well... they can certainly be fixed.
-
I have experienced some of these performance issues as well... they can certainly be fixed.
that would be wonderful +5%
-
Same latency issues today. I'm having a horrible time trying to keep up with the market, adjusting open orders taking far too long per order, some of them timing out bc of the delays. We're a new technology, so i get that we'll have technical growing pains, but this really needs to be a community priority to fix.
Imo as a market maker, you should use your own witness_node. :P
Good news is that bug mentioned above is solved yesterday, so the speed will be improved after next hard fork.
excellent! looking forward to the increased speed. trying to improve technical performance should be a never ending goal.
eh, you're probably right, i should run my own witness node, but i'm a little lazy with the tech stuff and just like to trade and crunch numbers :)
In a perfect world with all the resources in the world, yes, a dev might be assigned to do this. That's not the situation however. They devs are stretched thin as it is with all the demands placed on them for new features. Bug fixing and reliability should be even higher priority than performance IMO.
I can appreciate that you as a trader would like to see resources dedicated to squeezing every last drop of performance out of the code, however if you look at the situation objectively it should be clear you have some control over your performance problem - run your own node and stop being (in your words) lazy and (my words) selfish.
Look at all the usability issues raised with the stealth UI implementation for example. I don't think CNX was planning on the UI being as difficult to implement as it has been for them. UI is just not really in their wheelhouse (no offense svk, cass, but you two aren't the whole team).
Regarding the design choice to send redundant data to insure reliability thus causing more network traffic and incurring a performance penalty. That was a choice between reliability and performance that I'm sure there are ways to improve, but the general consensus is that performance of the UI in 2.0 using websockets is orders of magnitude greater than it was in the 1.0 era.
Good that you raised the concern tho, which was acknowledged by BM, but also this thread his provided you a solution which may not be the easiest for you to implement, but at least gives you an option you yourself can pursue. xeroc has quite a wealth of documentation on how to setup your own witness node. Check it out & give it a whirl. You might be surprised how easy it is and how much faster it may make your trades.
-
same error referenced in this thread, (now <= tx expiration) has been preventing me from claiming vesting bts for quite some time as well. this could bite us in the market cap someday if it's a common problem we take too long to fix and the fix enables somebody to dump later when they would've dumped earlier.
-
this is something I addressed today and should be improved within the next week or two.
-
I can appreciate that you as a trader would like to see resources dedicated to squeezing every last drop of performance out of the code, however if you look at the situation objectively it should be clear you have some control over your performance problem - run your own node and stop being (in your words) lazy and (my words) selfish.
if i wanted to run my own node, i'd already be doing it. i want to invest and i want to trade. We would be screwed if the only way to have a decent trading experience were to run your own node. the main point of this thread was to flag the issue to improve the user experience. thankfully, @bytemaster and his team were amazingly responsive and this issue can be put to bed.
-
I can appreciate that you as a trader would like to see resources dedicated to squeezing every last drop of performance out of the code, however if you look at the situation objectively it should be clear you have some control over your performance problem - run your own node and stop being (in your words) lazy and (my words) selfish.
if i wanted to run my own node, i'd already be doing it. i want to invest and i want to trade. We would be screwed if the only way to have a decent trading experience were to run your own node. the main point of this thread was to flag the issue to improve the user experience. thankfully, @bytemaster and his team were amazingly responsive and this issue can be put to bed.
Glad it worked out for you and everyone else. Just sayin tho, take action where you can and don't complain if others don't jump in to save you.
As I also said, glad you brought up the issue.
-
I can appreciate that you as a trader would like to see resources dedicated to squeezing every last drop of performance out of the code, however if you look at the situation objectively it should be clear you have some control over your performance problem - run your own node and stop being (in your words) lazy and (my words) selfish.
if i wanted to run my own node, i'd already be doing it. i want to invest and i want to trade. We would be screwed if the only way to have a decent trading experience were to run your own node. the main point of this thread was to flag the issue to improve the user experience. thankfully, @bytemaster and his team were amazingly responsive and this issue can be put to bed.
Glad it worked out for you and everyone else. Just sayin tho, take action where you can and don't complain if others don't jump in to save you.
As I also said, glad you brought up the issue.
thanks. i didn't mean to sound like i was unproductively complaining. I'm just trying to improve the user experience and will keep on pointing out bugs or other features i think can improve.
-
can the wallet choose the fastest node for the users?
Changing node is complex for average people.