I've just deployed this code to make browser <-> server communication more lightweight, and I've removed some of bet delays.
Anyway, you should see some bet speed improvement anyway, but the main limitation is still the speed of light, or rather speed the information travels through the universe. Before the browser can place a bet, a confirmation of the previous bet must be received, and if you live in another part of the world this itself could limit you to 2-4 bets per second. Our servers are in Ireland, so the closer you are, the faster your bets should be.
Tell me if you find anything not working as expected, it's been quite a large re-coding.
Cheers :-)
Ethan
Topic: 🔶 YOLOdice.com 🔶 suspended on 16st Mar 2021 - page 61. (Read 143533 times)
We were never streaming ALL the bets, so this should not be a huge problem...
I'll be deploying new code later today so we'll hopefully see a difference. I couldn't do it yesterday because I've discovered a few bugs and wanted to revise the code again.
Cheers,
Ethan
I'll be deploying new code later today so we'll hopefully see a difference. I couldn't do it yesterday because I've discovered a few bugs and wanted to revise the code again.
Cheers,
Ethan
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
Personally I dont care much about the bet speed nor bet history. I record my bets locally.
It would be great if bet results are broadcasted to all existing sessions for an account so
i can record bets placed on mobile on my pc the easy way
Whatever, here a few things I noticed which maybe help to increase the speed for general users:
The All bets stream ('Watch Bets') sucks a lot performance out of yolo and is enabled by default.
Same with the live updates for competitions. Especially on slow and mobile devices it slows down bets.
Thats a client side thing.
Even with Watch Bets disabled and non competition running I get like ~450 bets per minute (non delayed) using on-site Autoplayer.
Using my self made bot I get like 1k bets per minute. Thats 2 times faster! (* records from times before weekly competitions)
jfyi I use a slightly modified version of RGBkey´s API wrapper for NodeJs. Its modified the way I can auth by login instead of api key.
I think you can get much more out of yolo just by optimizing the web client!
Cheers notYou
Thats originally what i though the whole problem was about not the bet log ...figured it was the fact that like literally everybet streams on all bets tab n like you mentioned th comps
You got this @Ethan_nx i know you will come up with a solution!
*edit: As far as the chat history Im pretty sure doog stores those all on a seperate drive or server so maybe that could help if not to speed up just to clear some clutter
That sounds nice. do i have to change anything on my chat bot to keep working after update?
I don't think so. TCP API is unchanged. Older clients can still connect using JSON encoding, so you should be fine. The client needs to explicitely "ask" for msgpack encoding and the web app will do it.
I've tried to test everything as much as I could and I think it will work just GREAT :-)
Now, regarding the bet pruning - I got a lot of feedback and most people told us that keeping historical bets is NOT that important. Besides, most sites keep deleting old data anyway. I'll give the idea a few days, maybe I'll find a nice (technical) solution to keep old bets somewhere and keep them accessible, while having the recent data ultra-fast.
Thanks and cheers!
Ethan
So it seems bet speed is critical... OK, I started to work on optimizing browser <-> server communication and so far I was able to remove 75% of the overhead by switching to more efficient coding (msgpack), compressing keys and removing unnecessary messaging.
Right now everything seems to work. After I do the final code review I'll deploy the changes and remove some of the bet delays.
Right now everything seems to work. After I do the final code review I'll deploy the changes and remove some of the bet delays.
That sounds nice. do i have to change anything on my chat bot to keep working after update?
So it seems bet speed is critical... OK, I started to work on optimizing browser <-> server communication and so far I was able to remove 75% of the overhead by switching to more efficient coding (msgpack), compressing keys and removing unnecessary messaging.
Right now everything seems to work. After I do the final code review I'll deploy the changes and remove some of the bet delays.
Right now everything seems to work. After I do the final code review I'll deploy the changes and remove some of the bet delays.
YOLOdice players, we would like your opinion!
Record bets in separate public database
I'm a fan of increasing the speed, but keeping the historical bets available through a different server -- they hybrid option you were speaking of.
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
Personally I dont care much about the bet speed nor bet history. I record my bets locally.
It would be great if bet results are broadcasted to all existing sessions for an account so
i can record bets placed on mobile on my pc the easy way
Whatever, here a few things I noticed which maybe help to increase the speed for general users:
The All bets stream ('Watch Bets') sucks a lot performance out of yolo and is enabled by default.
Same with the live updates for competitions. Especially on slow and mobile devices it slows down bets.
Thats a client side thing.
Even with Watch Bets disabled and non competition running I get like ~450 bets per minute (non delayed) using on-site Autoplayer.
Using my self made bot I get like 1k bets per minute. Thats 2 times faster! (* records from times before weekly competitions)
jfyi I use a slightly modified version of RGBkey´s API wrapper for NodeJs. Its modified the way I can auth by login instead of api key.
I think you can get much more out of yolo just by optimizing the web client!
Cheers notYou
Good points. This could help for sure!
Edit: I have to admit, during the 3 years of adding new features the client <-> server communication got a bit bulky and it might be good to revise and optimize it. Making the messages less bulky would definitely speed things up!
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
Personally I dont care much about the bet speed nor bet history. I record my bets locally.
It would be great if bet results are broadcasted to all existing sessions for an account so
i can record bets placed on mobile on my pc the easy way
Whatever, here a few things I noticed which maybe help to increase the speed for general users:
The All bets stream ('Watch Bets') sucks a lot performance out of yolo and is enabled by default.
Same with the live updates for competitions. Especially on slow and mobile devices it slows down bets.
Thats a client side thing.
Even with Watch Bets disabled and non competition running I get like ~450 bets per minute (non delayed) using on-site Autoplayer.
Using my self made bot I get like 1k bets per minute. Thats 2 times faster! (* records from times before weekly competitions)
jfyi I use a slightly modified version of RGBkey´s API wrapper for NodeJs. Its modified the way I can auth by login instead of api key.
I think you can get much more out of yolo just by optimizing the web client!
Cheers notYou
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
I would prefer faster bets. It takes over 30 minutes for me to get 1,000 bets using autoplayer. Being able to lookup any bet is a nice feature to have but I rarely ever use it.
....
speed is more favoreable to me when it comes to playing dice or just any other gambling . while finding older bets is also important like if there are mini games like roll hunts so that you can check your bet histroy if you missed seeing it.
50 to 100 bets on histroy is already ideal to me but more than that does not already make sense. why would someone want see more older bets ? i think that only cause alot of lag on the site and on the user experience .
YOLOdice players, we would like your opinion!
A topic that comes up often for many players is bet speed: What can YOLOdice do to make bets faster?
First, you must understand that bet speeds are determined largely by your own internet speed, but also your distance from the YOLOdice servers. For example the servers are in Europe (Ireland), so players in EU will tend to have much higher bet speeds than players in the USA, or the Philippines, which are much further away. However, there's another important factor that tends to get forgotten (this is the important one for this discussion): How much of the site's bet history is available on-demand?
In YOLOdice's case, we have every single bet placed (nearly 7 BILLION) instantly available for players to look at whenever they please. However, if we were to limit this stored bet amount, to something like the last 250 Million bets placed, or only bets placed within the last month, according to Ethan, we could significantly decrease induced bet delays, and bet speed in general for regular bets would likely improve (but again, distance from server and internet speed matter the most for this).
So here's the million-dollar question we'd like you guys to form your opinions on:
Would you prefer to have access to all bets placed on YOLOdice (as it is now), or increased bet speeds but without on-demand older bets?
YOLOdice players, we would like your opinion!
A topic that comes up often for many players is bet speed: What can YOLOdice do to make bets faster?
First, you must understand that bet speeds are determined largely by your own internet speed, but also your distance from the YOLOdice servers. For example the servers are in Europe (Ireland), so players in EU will tend to have much higher bet speeds than players in the USA, or the Philippines, which are much further away. However, there's another important factor that tends to get forgotten (this is the important one for this discussion): How much of the site's bet history is available on-demand?
In YOLOdice's case, we have every single bet placed (nearly 7 BILLION) instantly available for players to look at whenever they please. However, if we were to limit this stored bet amount, to something like the last 250 Million bets placed, or only bets placed within the last month, according to Ethan, we could significantly decrease induced bet delays, and bet speed in general for regular bets would likely improve (but again, distance from server and internet speed matter the most for this).
So here's the million-dollar question we'd like you guys to form your opinions on:
Would you prefer to have access to all bets placed on YOLOdice (as it is now), or increased bet speeds but without on-demand older bets?
last years worth of bets should be enough.......we all want faster bets
Cheers Jon
YOLOdice players, we would like your opinion!
A topic that comes up often for many players is bet speed: What can YOLOdice do to make bets faster?
First, you must understand that bet speeds are determined largely by your own internet speed, but also your distance from the YOLOdice servers. For example the servers are in Europe (Ireland), so players in EU will tend to have much higher bet speeds than players in the USA, or the Philippines, which are much further away. However, there's another important factor that tends to get forgotten (this is the important one for this discussion): How much of the site's bet history is available on-demand?
In YOLOdice's case, we have every single bet placed (nearly 7 BILLION) instantly available for players to look at whenever they please. However, if we were to limit this stored bet amount, to something like the last 250 Million bets placed, or only bets placed within the last month, according to Ethan, we could significantly decrease induced bet delays, and bet speed in general for regular bets would likely improve (but again, distance from server and internet speed matter the most for this).
So here's the million-dollar question we'd like you guys to form your opinions on:
Would you prefer to have access to all bets placed on YOLOdice (as it is now), or increased bet speeds but without on-demand older bets?
Tough call its nice to be able to see all bets but we might have to compromise guys I'm guessing thats what happened with dooglus on just-dice since you cannot see every bet placed on JD if there are a lot of users running bots or playing in general ...maybe we can do a public vote?
I miss understood what the issue was so as far as the log of bets taking up too much space maybe hosting those seperately could be a solution
YOLOdice players, we would like your opinion!
A topic that comes up often for many players is bet speed: What can YOLOdice do to make bets faster?
First, you must understand that bet speeds are determined largely by your own internet speed, but also your distance from the YOLOdice servers. For example the servers are in Europe (Ireland), so players in EU will tend to have much higher bet speeds than players in the USA, or the Philippines, which are much further away. However, there's another important factor that tends to get forgotten (this is the important one for this discussion): How much of the site's bet history is available on-demand?
In YOLOdice's case, we have every single bet placed (nearly 7 BILLION) instantly available for players to look at whenever they please. However, if we were to limit this stored bet amount, to something like the last 250 Million bets placed, or only bets placed within the last month, according to Ethan, we could significantly decrease induced bet delays, and bet speed in general for regular bets would likely improve (but again, distance from server and internet speed matter the most for this).
So here's the million-dollar question we'd like you guys to form your opinions on:
Would you prefer to have access to all bets placed on YOLOdice (as it is now), or increased bet speeds but without on-demand older bets?
Tough call its nice to be able to see all bets but we might have to compromise guys I'm guessing thats what happened with dooglus on just-dice since you cannot see every bet placed on JD if there are a lot of users running bots or playing in general ...maybe we can do a public vote?
YOLOdice players, we would like your opinion!
A topic that comes up often for many players is bet speed: What can YOLOdice do to make bets faster?
First, you must understand that bet speeds are determined largely by your own internet speed, but also your distance from the YOLOdice servers. For example the servers are in Europe (Ireland), so players in EU will tend to have much higher bet speeds than players in the USA, or the Philippines, which are much further away. However, there's another important factor that tends to get forgotten (this is the important one for this discussion): How much of the site's bet history is available on-demand?
In YOLOdice's case, we have every single bet placed (nearly 7 BILLION) instantly available for players to look at whenever they please. However, if we were to limit this stored bet amount, to something like the last 250 Million bets placed, or only bets placed within the last month, according to Ethan, we could significantly decrease induced bet delays, and bet speed in general for regular bets would likely improve (but again, distance from server and internet speed matter the most for this).
So here's the million-dollar question we'd like you guys to form your opinions on:
Would you prefer to have access to all bets placed on YOLOdice (as it is now), or increased bet speeds but without on-demand older bets?
Very cool new "something new" update guys! I think the real-time update is not something every other wager contest has so that is something really nice to see. Congrats to the first 2020 winners:)
That is a total value of almost $4000 in prizes,,, I know, BTC is down now but 10k soon right everyone?
That is a total value of almost $4000 in prizes,,, I know, BTC is down now but 10k soon right everyone?
I've just sent the prizes for the first weekly round. The next round has ~0.4 BTC in prize pools (in BTC+LTC+ETH+DOGE) and 10 prizes for each coin (=40 together). Don't miss it! https://yolodice.com/#weekly
Cheers,
Ethan
Cheers,
Ethan
Jump to: