-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add threaded-timer support to hpc-benchmark #14
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR!
timer_array = tuple(d[timer][tid] - intermediate_kernel_status[timer][tid] for tid in range(len(d[timer]))) | ||
d[timer] = timer_array[0] | ||
d[timer + "_max"] = max(timer_array) | ||
d[timer + "_max"] = min(timer_array) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: d[timer + "_max"] = min(timer_array)
must be d[timer + "_min"] = min(timer_array)
timers = ['time_collocate_spike_data', 'time_communicate_prepare', | ||
'time_communicate_spike_data', 'time_deliver_spike_data', | ||
'time_gather_spike_data', 'time_update', 'time_simulate'] | ||
timers = ['time_collocate_spike_data', 'time_communicate_prepare', 'time_communicate_spike_data', 'time_communicate_target_data', 'time_construction_connect', 'time_construction_create', 'time_deliver_secondary_data', 'time_deliver_spike_data', 'time_gather_secondary_data', 'time_gather_spike_data', 'time_gather_target_data', 'time_omp_synchronization_construction', 'time_omp_synchronization_simulation', 'time_mpi_synchronization', 'time_simulate', 'time_update'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Construction related timers like time_construction_connect and time_gather_target_data should not be used later for subtraction of the presim timers, since they are not part of the presim time. The logfiles should only contain these timers once without distinction into presim and sim.
d[timer] -= intermediate_kernel_status[timer] | ||
if type(d[timer]) == tuple or type(d[timer]) == list: | ||
timer_array = tuple(d[timer][tid] - intermediate_kernel_status[timer][tid] for tid in range(len(d[timer]))) | ||
d[timer] = timer_array[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason for adding only the first value of the tuple to the logfile? And why is this handled differently for the presim timers?
Merge this as soon as nest/nest-simulator#3378 is merged into NEST