Antoine Pitrou
Antoine Pitrou
> I noticed the integration tests linked involve files - perhaps the byte order for Arrow files is different from the in-memory byte order (big-endian vs little-endian)? No, it's probably...
Well, you'll have to thank @tustvold for that :-)
The cron job would need to run new benchmarks as well, see instructions in https://github.com/spacetelescope/asv/issues/278
When benchmarking local changes, I also find `asv dev` to be very useful. Not sure it needs to be mentioned in the README, though.
I think we should also have guidelines for benchmarks: - have individual `time_xxx` methods take on the order of 100-300 ms if possible (obviously some workloads will need more), so...
Another issue: which timer function should be used? asv's default timer may not be adequate: https://asv.readthedocs.io/en/latest/writing_benchmarks.html#timing Should we measure CPU time or wallclock time? IMHO we should measure wallclock time:...
Other question: I see a couple of existing benchmarks parameterize on the `get` function (`multiprocessing.get`, `threaded.get`, etc.). Is this useful/desired? What are we trying to achieve here?
@mrocklin
Closed & re-opened to try and schedule a Travis build.
> I wasn't able to get the job scheduler to reliably use the environment variables. You mean set them? Or are they set manually by the system administrator?