Scaling

WIP

In terms of how the trader performs when given more funds I don't see too much of a scaling issue here. With more funds the operator might feel more comfortable reducing the straddle, especially if they don't having to give up coverage to do so. Trade frequency would go up with a smaller straddle but requests are still subject to exchange throttling. BlueCollar can't trade faster than the exchange limits. This would however create more rows in the database, so there may end up being an issue there. Though it seems that issues arising from that could be resolved with query optimization, a data archiving strategy, a data limiting strategy, etc.

A possible limiting factor preventing the straddle from ever becoming to small would be an increase in the occurrences of taker fees that occur with a very small straddle.

With a stack of funds large enough I could see a potential issue with the trader calculating a quantity that results in placing undesirable buy and sell walls on the exchange. BlueCollar thrives on volatility so if it's doing anything to hinder that then it's working against itself. The easiest option is to use the RESERVE setting to keep some of the funds out of the traders hands. Another option would be to trade a more expensive crypto, as per trade quantity won't get calculated as high. But these don't seem like ideal options for most situations.

The better long term scaling solution is running multiple instances of BlueCollar on multiple exchanges, and/or multiple instances on a single exchange trading different cryptos, e.g., Bitstamp sub-accounts.