Post
Topic
Board Gambling
Re: 🔶 YOLOdice.com 🔶 WEEKLY COMPETITIONS - 0.4 BTC guaranteed, 40 prizes!
by
Bluewaffle
on 23/01/2020, 01:39:54 UTC
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?

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 Grin

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