New Backtesting Cloud

The cloud has been successfully deployed with 0-downtime. Nice work Andrew Hart!

Well done folks. It seems to work like a breeze. Mega Kudos =-)

I've been having problems saving algos and loading live paper trading algos, everything seems slow :( even tried different browsers.

Everything(especially saving) is working for me now, thank you!
Cloud scalability is a really exciting upgrade for the community, thanks QC team!

Hi Jared, is that just me or is the backtesting platform slow again. Each of my simple backtests are taking ages to run . that is when they run at all (one equity, 3 days of data). What's creating this?

Yes, backtesting has been slow for me for 2 days now. It takes hours for backtests that used to be completed in 5 min, unfortunately.

Sdoofsam jaafari - there were teething problems for the scaling to keep up with demand the first night but now running as normal. 

Seems a lot faster now than prior!

Thank you for looking into the speed issues!

I know this is a separate topic that I'm about to mention - is there a feature request/wishlist thread? Speed and debugging has been my biggest hurdle with quantconnect. Seems the speed is getting sorted out and would love to have better debugging mechanism. It's very time consuming finding what part of an algorithm is throwing the errors (or why).

Thanks for all that you do!

Hi Charles,

I second your motion.  BTW, here's what I'm doing for as a workaround. There may be a better way, so I'm all ears as to better methodologies.

rather than being clueless as to where my errors occurred or trying to decipher extremely crpytic error codes produced by the log files, I do this

at top  of algo use a constant

VERBOSEMODE = True

Then inside each procedure or function I use try except statements, with "reached line number" and optional varriable logging code. Here's the pseudcode sample:

def someFunction(self,somevar):

    try:

        someVar = 1

        if VERBOSEMODE: self.Log("got past line 5 of someFunction with somevar = {}". format(someVar)  )  

        someOtherBrokenVar = 42.000 / 0 

    if VERBOSEMODE: self.Log("got past line 7 of someOtherBrokenFunction with somevar = {}". format(someOtherBrokenVar)  )  

   except:       
          self.Log('An unknown error occurred running someFunction  ' +  str(sys.exc_info()[0]) )                 
 

So this code would pass first level variable definition and bomb on second one (division by zero). You would have a clue up to where your code ran fine and an idea about type of error causing problems

If you later get tired of seeing all the log files, simply erase those lines or turn VERBOSEMODE to False.

Hope that helps someone. Now if some bright python guru could tell me how to automatically generate the linenumber (so I don't have to handcode them) as well as function name, it would be even simpler.

Hi

I have been having lots of issues with the new backtesting system. Either the backtest will take ages to launch or it will launch as normal but the backtest will crash. Additionally, the usual backtest tearsheet is not being generated. Are you aware of similar issues?

Thanks

Jonny