Skip to content
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

Improve timeit stats. #49

Open
1uc opened this issue Sep 20, 2023 · 0 comments
Open

Improve timeit stats. #49

1uc opened this issue Sep 20, 2023 · 0 comments

Comments

@1uc
Copy link
Contributor

1uc commented Sep 20, 2023

I have the following log file:

$ cat /gpfs/bbp.cscs.ch/data/project/projXX/jobs/ps/2023/09/68/1724368-2023-09-15T09:47:08-pydamus-0.log
[STEP] (Sep.15 10:23:00) ==> CYCLE 28 (OUT OF 32)
...
[STEP] (Sep.15 10:24:13) ==> CYCLE 29 (OUT OF 32)
...
[INFO] (Sep.15 10:29:06) +========================================= TIMEIT STATS (Cycle Run 28) =========================================+
[INFO] (Sep.15 10:29:06) |                       Event Label                        | Avg.Time | Min.Time | Max.Time | Hits R0 / Total   |
[INFO] (Sep.15 10:29:06) +---------------------------------------------------------------------------------------------------------------+
[INFO] (Sep.15 10:29:06) | Compute LB                                               |     0.00 |     0.00 |     0.00 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Cell creation                                            |     0.54 |     0.54 |     0.54 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Synapse creation                                         |    24.64 |    24.64 |    24.64 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Enable Stimulus                                          |     0.00 |     0.00 |     0.02 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Enable Modifications                                     |     0.00 |     0.00 |     0.00 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Enable Reports                                           |     0.90 |     0.90 |     0.90 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | Model Finalized                                          |     2.65 |     2.65 |     2.65 |       1 / 400     |
[INFO] (Sep.15 10:29:06) |  ╚ stdinit                                               |     2.61 |     2.61 |     2.61 |       1 / 400     |
[INFO] (Sep.15 10:29:06) | corewrite                                                |     3.68 |     3.68 |     3.68 |       1 / 400     |
[INFO] (Sep.15 10:29:06) +---------------------------------------------------------------------------------------------------------------+
[INFO] (Sep.15 10:29:06) +========================================= TIMEIT STATS (Final Stats) ==========================================+
[INFO] (Sep.15 10:29:06) |                       Event Label                        | Avg.Time | Min.Time | Max.Time | Hits R0 / Total   |
[INFO] (Sep.15 10:29:06) +---------------------------------------------------------------------------------------------------------------+
[INFO] (Sep.15 10:29:06) | finished Run                                             |     0.05 |     0.00 |     0.05 |       1 / 400     |
[INFO] (Sep.15 10:29:06) +---------------------------------------------------------------------------------------------------------------+

I would find it useful if each of the Cycle Run tables would include a total. Likewise it would be useful if there where a total duration of the entire run; not just the duration of the simulation. Finally, when summing the runtime of all rows in a Cycle Run table, it differs from the total time it took to run that cycle. This might indicate that a heavy component isn't being timed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant