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
Currently run_one() does not call get_default_parameters(), so while benchmark parameter defaults are used when running, if not specified they will not show up in tags as they should.
One way to deal with this would be to call get_default_parameters() on the params and ensure the result has exactly one row. (Note we can't do this right now, because voltrondata-labs/benchmarks is sending cpu_count = NULL to run_one(), which run_one() is currently interpreting as "do nothing about CPU count in the script", whereas get_default_params() will turn that into c(1L, parallel::detectCores()). For Arrow in particular, arrow:::GetCpuThreadPoolCapacity() appears equal to parallel::detectCores(), but changing the way we set it may set the cpu_count tag and break histories. We probably should, but will need to go clean them up.)
Alternately we could validate based on formals(bm$setup) and insert or error if any are not specified, but maintaining an alternate version of get_default_params() would increase the complexity and maintenance burden.
The text was updated successfully, but these errors were encountered:
Currently
run_one()
does not callget_default_parameters()
, so while benchmark parameter defaults are used when running, if not specified they will not show up in tags as they should.One way to deal with this would be to call
get_default_parameters()
on the params and ensure the result has exactly one row. (Note we can't do this right now, because voltrondata-labs/benchmarks is sendingcpu_count = NULL
torun_one()
, whichrun_one()
is currently interpreting as "do nothing about CPU count in the script", whereasget_default_params()
will turn that intoc(1L, parallel::detectCores())
. For Arrow in particular,arrow:::GetCpuThreadPoolCapacity()
appears equal toparallel::detectCores()
, but changing the way we set it may set thecpu_count
tag and break histories. We probably should, but will need to go clean them up.)Alternately we could validate based on
formals(bm$setup)
and insert or error if any are not specified, but maintaining an alternate version ofget_default_params()
would increase the complexity and maintenance burden.The text was updated successfully, but these errors were encountered: