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
@NickCrews, if i understand the benchmarking code correctly, the first time a benchmark runs it will create a settings file, and then in all subsequent runs, the benchmarking code will use that settings file.
It would be very helpful if we could separate this out, so we had benchmarks runs where each run there was not training, and other runs where each run used a settings file.
does that make sense?
The text was updated successfully, but these errors were encountered:
Yes that makes sense and is possible. Will try to get to this in next couple days.
Also do you think adding a larger dataset would be useful? Not sure how meaningful these small datasets are, eg howuch of that 50Mb of peak memory you mentioned is just overhead
@NickCrews, if i understand the benchmarking code correctly, the first time a benchmark runs it will create a settings file, and then in all subsequent runs, the benchmarking code will use that settings file.
It would be very helpful if we could separate this out, so we had benchmarks runs where each run there was not training, and other runs where each run used a settings file.
does that make sense?
The text was updated successfully, but these errors were encountered: