My advice here was pretty standard - profile, find bottlenecks, use caching/vectorization/numpy/numba to speed up the hot code.
But even better advice is "do less backtesting" (as pointed out by @therobotjames)https://twitter.com/Overlevered_AM/status/1382201962687557638 …
-
-
Monetizing the prediction is the job of portfolio construction (where you trade off alpha vs. risk, costs and constraints).
Show this thread -
The backtest is just to make sure that all these parts are working together as expected. In many ways a slow backtest can be a feature, because it discourages you from running hundreds of simulations and optimizing based on the results!
Show this thread
End of conversation
New conversation -
-
-
Great thread! What if the factor regression approach show hardly 50% hit rate for next 1-6 months horizon (like most of the textbooks examples) but the backtest on this signal is promising?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.