You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently found that for benchmarking "can we make $ trading", we need 178 days worth of sims (50K 5-min candles). 17.8 days (5K candles) is not enough.
But running 178 days takes a long time. On Trent's MacBook Pro M3, it takes about 3 h for one run.
We can probably optimize a lot for << 3h, via the typical flow: run profiling, fix the worst offender, repeat, until diminishing returns. I'll create an issue.
But we might get a quick win: what if we set train_every_n_epochs to be >> 1? Model-building is likely the biggest bottleneck. The question is: how much does that impact "trader profitability" numbers?
TODOs
do a benchmark comparing train_every_n_epochs at various values: 1, 100, 500, 1000; and see what the difference is.
Track: trader profit vs time (and final value), and predictoor profit vs time (and final value).
Report those results in this github issue, simply by screenshots of the plots.
The text was updated successfully, but these errors were encountered:
trentmc
changed the title
[Model/train] Can we get away with train_every_n_epochs > 1?
[Model/trade] Can we get away with train_every_n_epochs > 1?
Jul 17, 2024
Background / motivation
We recently found that for benchmarking "can we make $ trading", we need 178 days worth of sims (50K 5-min candles). 17.8 days (5K candles) is not enough.
But running 178 days takes a long time. On Trent's MacBook Pro M3, it takes about 3 h for one run.
We can probably optimize a lot for << 3h, via the typical flow: run profiling, fix the worst offender, repeat, until diminishing returns. I'll create an issue.
But we might get a quick win: what if we set train_every_n_epochs to be >> 1? Model-building is likely the biggest bottleneck. The question is: how much does that impact "trader profitability" numbers?
TODOs
The text was updated successfully, but these errors were encountered: