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
With all the NEST benchmarking efforts going on, do you have (plan) a model for estimating wall times? Aka some function returning wt=f(N_pops, K_conns, N_mpi, N_proc, t_sim, ...)
I'm thinking of something for the LFP predictions which may have to be broken down into parallel jobs in the macaque v1 case.
The text was updated successfully, but these errors were encountered:
Such a function would not be trivial since these parameters depend strongly on the machine. For network construction, the specific connection routines are very different in terms of their wall-clock time. So far, we do not have such general estimates but per-model examples to compare with.
Let's not overcomplicate this. For now all simulations run on one HPC resource (well perhaps also JUSUF which is anyway similar). We also need only to consider one connection routine (distance-dependent) which is already a worst case scenario. For the sake of brewity, let N_mpi and N_proc be constants, what I had in mind for the network is that create times would be approximately linearly dependent on N_pops.sum(), connect times perhaps with some exponential dependency so proportional with K_conns^c and run times again linearly dependent on t_sim * N_pops.sum() etc.
wt = a * N_pops.sum() + b * (K_conns^c).sum() + d * t_sim * N_pops.sum() + ..
As you are have set up different network sizes (mesocircuit etc.) could we not estimate expected wall times a priori if thesse coefficients can be fitted? If not, what strategy do you have when setting wall times which for now are hardcoded in the base_system_params file?
With all the NEST benchmarking efforts going on, do you have (plan) a model for estimating wall times? Aka some function returning wt=f(N_pops, K_conns, N_mpi, N_proc, t_sim, ...)
I'm thinking of something for the LFP predictions which may have to be broken down into parallel jobs in the macaque v1 case.
The text was updated successfully, but these errors were encountered: