Topic: RollerBot - Alpha testing begins soon! - page 6. (Read 18644 times)

This looks extremely cool, even if I do not yet completely understand all of its potential capabilities. I'm not a programmer, but if you are ever looking for someone to team up with on a web based GUI, feel free to hit me up.

It looks excellent so far.
This could change trading for the better in a short time.
Keep up the great work I cannot wait to try it.

HHVM is now compiling on the backend server.  Hopefully I can test running the Rollerbot code through the HHVM compiler tonight!  I already have benchmarks finished running the code through the PHP interpreter, so this should turn out interesting!

Lots of good stuff today.

The new API cache daemon system is running great on the backend.  Right now it's only running against Cryptsy and BTC-e (mainly because I haven't updated the other exchanges yet to use the new system).  Those two exchanges alone are cacheing 542 API calls in real-time effortlessly.  The daemon thread monitor script is doing an excellent job of throttling the API calls(by spawning and removing parallel daemon scripts) to keep the age of the data at the desired setpoint.  
Tonight I should be able to update all the exchanges to use the new methods and get a full load test in.
Next on the plate is to get backend plugins running, at which time I'll be able to start storing trade history to the database again.

I've also drastically reduced the number of database queries.  Up until this point, I was storing the nonce for each account API in the database, querying to retrieve it each call, then querying again to increment the value.  With so many API calls, this was adding up to thousands of queries per second, which are now eliminated due to using a better method based on microtime instead.

The exchange landscape is really looking good lately. I've seen quite a few new exchanges popping up in the last month, almost all of them with a full trade API.  I fully expect to support 20+ exchanges by the time Rollerbot launches!

Other good news is that HHVM recently included mysqli support, so soon I will be running everything through the HHVM JIT compiler for a huge speed boost and better memory management.


Here is a screenshot of one of the daemons running in the background.  If you look across the bottom,  you'll see that the daemon spawned 22 parallel threads, with 5 symbols being queries per thread (this specific daemon is querying cryptsy for trade data).  If the queries take too long, then more threads are spawned until the average execution time is where it should be.

looking good

march 15th ish sounds good seems you moving pretty well

That will be great.
I'm not good at trading on my own and this would be a godsend.
Thanks

Daily update on the thread.

The new api daemon system (including new cache integration and load throttling) has been the focus for the day.  It's about 75% done at the moment -  all of the backend daemon changes are done (mainly common (public) API calls).  I just have to get the frontend to start it's own daemon process for individual authenticated user API calls.

For now I've limited my tests to cryptsy.  Over 320 API calls have to be cached in the background.  In my tests, this throttled to just under 40 threads, keeping the local cache at 10 seconds of age.  Each additional user only adds 2 API calls to the total - so you can see where the heaviest lifting is done on the backend server and that adding additional users has very low impact on the overall load.  Anyways, in my tests tonight the processor usage was much lower than expected (0.03 as reported by top).

Moving forward, I have to finish adapting the rest of the exchanges to use the new daemon and cache system, and add the ability to the plugin system to have backend plugins (to be used by the Rollerbot Platform, such as plugins to store trade data to the database), as well as frontend plugins (to be used by individual users, such as trade bot plugins).

Lastly, I started drafting a plugin API.  This one is a ways out, be eventually I hope to provide an API to interface the Rollerbot platform for those who wish to code their own plugins.  I'll probably open-source at least one or two of the simpler plugins as examples.  This will let users that have programming experience program their own plugins (and even share them systemwide with Rollerbot users if they want).  In all actuality it will be the same API that I use to make the plugins, but with the plugin includes dynamically included to protect the source code behind Rollerbot (in which case it's more of an issue of documentation).

That should be it for the night.  I'll check back in tomorrow.  There is a good chance that the entire backend should be back up and running tomorrow and I can actually get some real-life benchmarks.

Thanks for stopping in!
It's nice to hear from from someone that understands the choices in underlying technology (as well as the difficulty in implementing some of it). 
It was pretty hard to take a step back from a perfectly running system only to tear it down and implement things properly for a fully scalable commercial system.  It is delaying the launch date, but in the end things will be done correctly and it will be worth it. 

I'll be in touch!

As a software developer of 15 years, your approach and choice of technology sounds spot-on to me, and so I've registered on this forum simply to request to be a beta tester when you're ready.  I have plenty of Linux command line experience (if that's still a concern now that you're building a UI), and I'm excited to see the project progress!


zebaroo

Just popping in real quick.
I spent most of today getting the Amazon AWS redis Elasticache setup.  Everything seems to be working now, so now I need to go through the code that uses the old disk-based cache and update it to use the blazing fast redis cache.  Considering that the cache is normally under a 500+ I/O per second load, this should end up being a tremendous speed-up due to reducing all that disk I/O.

I also have the database fully setup on the new server.  Hopefully these next changes go smoothly and I can actually fire the rollerbot backend up very soon to start storing trade history locally again.

Sounds awesome! Would love to help on the beta tester side at the least

This looks awesome! Put me in for beta tester and reseller if you are planning to accept that!

In time I'll go through all of the beta test requests and send out some information.  I'm going to do my best to get as many of you guys as possible into the beta to give things a good test.  My goal is to have things ready by March 15th to kick off the beta.  If things go well, hopefully even sooner

Hi there


Any chance to join the Beta Test, the Tool looks really awesome!

best regards


Hektek

Looks good Jon!

Just posting some shots of the progress so far.
The UI is coming along nicely.  The user registration/authorization/authentication system is up and working.
Exchange accounts can be added/edited/deleted from your profile
Strategy names and descriptions can now be Added/edited/deleted. 

Much of the work now has to go into the strategy system.  This is how setting up your account and strategies will work:
- After registration, you go into your profile settings and add Exchange accounts.  You can setup multiple accounts per exchange, and select from all of the supported exchanges Rollerbot has to offer.
- After you have all of your exchange accounts set up (more can be added at any time), then you will be ready to create your first strategy.  Under the "Strategies" tab you will create a strategy name and description.  Selecting one of these strategies once entered will bring you to an area where the strategy can be configured.  This will be done by selecting one or more of your accounts, defining the trade pairs for each account, then finally which trading plugins you want to run for each trade pair for each account.  You will be able to configure this any way you want - multiple plugins per trade pair (even multiple instances of the same plugin), one plugin per tradepair - whatever you want.
- Manage your settings.  Each plugin instance has it's own settings group.  For every single plugin under every tradepair under every account you have individual settings so that you can fine-tune your strategy.
- Make as many strategies as you want.  Only one strategy can be active at a time, but you can switch between them on the fly.  Switch to a high risk strategy during times of high market volatility, and then to a lower risk hold position during flat market times with one click.


Here are some sneak peeks of the UI so far:

Exchange accounts list:


Editing existing account:


Adding new account:


Strategies list:


Editing a strategy:



Back to work!

looks fantastic. count me in for testing or any other help you need.

I have not done as much trading as I would like due to the difficulty in messing around on each exchange so much.
When you are ready for testers I would like to be one for it.

Really looking forward to seeing updates, the screenshots specifically!