Of all the worker projects on the table, making the DEX faster should be #1

[cylonmaker2053]

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.

[abit]

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. 
Good news is that bug mentioned above is solved yesterday, so the speed will be improved after next hard fork.

[Bhuz]

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?

[Shentist]

i have no problems today!

[EstefanTT]

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 ?

[cylonmaker2053]

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.

[cylonmaker2053]

@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...

[cylonmaker2053]

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]

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.

[merivercap]

@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!

[svk]

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?

[cube]

A workaround:

Try a different API connection server.  If this is still too slow, run your own node.

[cylonmaker2053]

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.