Lena

@magick93, the data is saved to the disc at `~/.catalyst/data/live_algos/` directory, using `pickle`. @Amarchuk > Or we just put everything we can restore to context and pass it to `initialize`?...

@sam31415, thanks for reporting this and opening an issue here as well. Adding a reference to the [forum report.](https://catalyst.enigma.co/t/cpu-usage-constantly-increasing-on-google-cloud-vm/216) Have you been experiencing this phenomena when running not only on...

I meant the number of trading pairs used. Your algorithm above seems to run on all the exchange pairs (=entire universe), so I was wondering whether this behavior was observed...

Thanks @avolution for this suggestion.

Thanks for reporting @brandsimon, we will investigate.

Hi @kooomix , In live/paper trading only the minute frequency is supported. Thanks for reporting this, we will update our documentation (we added this to the [API doc](https://enigma.co/catalyst/appendix.html) but it...

Hi @kooomix , Actually we will be happy to hear your feedback. We were not sure that such a low frequency is required in live mode. Lena

Thanks for the feedback. We will add this to our future features list. In the meantime, you could do something like this to run your code at a lower resolution...

Hi @kooomix , you mean that the workaround suggested above isn't satisfying in terms of performance? Thanks for the feedback, the only solution is to support more frequencies (I've edited...

Hi @kooomix , the workaround suggested by @embaral shouldn't call your `handle_data` every minute but in the frequency you have defined (1 hour for example), which might have an affect...