dodging memory issues during detailed macro benchmarking

[EmilRehnberg]

Hi! @jimhester
I've been trying to benchmark code that's a bit larger with a number of different parameters. But I end up getting problems due to that each run does ~100-300 MB memory allocations and the $memory part of the press results takes up huge memory after a few runs.

Is there a way to get the detailed benchmarking time results from press and mark but get away from the memory head aches? E.g. disable the memory checks?

[jimhester]

You can use bench::bench_time() directly.

[EmilRehnberg]

I'll refer to the discussion in the #62
I can see the use of going with bench::bench_time() by combining a list with arguments and purrr::pmap