-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate Profiling Stats #557
Labels
Comments
thcrock
added a commit
that referenced
this issue
Dec 27, 2018
- Add cProfile bindings to experiment.run, write to profiling_stats directory in project path. - Add local_fs_path method to Storage classes so modules that need a filename to write to (e.g. cProfile) can still use Project Storage. - Add cli option for profiling - Add section on profiling to docs
thcrock
added a commit
that referenced
this issue
Dec 27, 2018
- Add cProfile bindings to experiment.run, write to profiling_stats directory in project path. - Add local_fs_path method to Storage classes so modules that need a filename to write to (e.g. cProfile) can still use Project Storage. - Add cli option for profiling - Add section on profiling to docs
thcrock
added a commit
that referenced
this issue
Dec 27, 2018
- Add cProfile bindings to experiment.run, write to profiling_stats directory in project path. - Add local_fs_path method to Storage classes so modules that need a filename to write to (e.g. cProfile) can still use Project Storage. - Add cli option for profiling - Add section on profiling to docs
thcrock
added a commit
that referenced
this issue
Jan 2, 2019
- Add cProfile bindings to experiment.run, write to profiling_stats directory in project path. - Add cli option for profiling - Add section on profiling to docs
thcrock
added a commit
that referenced
this issue
Jan 3, 2019
- Add cProfile bindings to experiment.run, write to profiling_stats directory in project path. - Add cli option for profiling - Add section on profiling to docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should be able to generate profiling stats for individual experiment runs, utilizing Python's builtin cProfile. Each experiment is different and will spend its time in different places, so this type of functionality should be available for anybody to use and not just run against dirty duck.
The text was updated successfully, but these errors were encountered: